MRatWork Forum by Mustafa Ramadhan
Sawo Project - Kloxo-MR Discussions => Kloxo-MR Development => Topic started by: fossxplorer on 2014-09-16, 13:51:33
-
[root@mail ~]# service named start
Starting named:
Error in named configuration:
/etc/named.conf:10: open: /home/bind/conf/defaults/named.acl.conf: file not found
[FAILED]
[root@mail ~]#
ALL MY SITES ARE DOWN DUE TO THE DNS SERVICE IS DOWN!
How do i fix this?
-
switch to other (like djbdns) and switch back to djbdns.
Upgrade must be running 'sh /script/cleanup'.
-
Ok, i'll try.
Already done 'sh /script/cleanup'. after the upgrade.
switch to other (like djbdns) and switch back to djbdns.
Upgrade must be running 'sh /script/cleanup'.
-
Switching to DJBDNS works, but switching back to BIND doesn't.
It looks like something goes very wrong.
When i chose back BIND, i couldn't find /etc/init.d/djbdns nor /etc/init.d/named.
Also, yum logs shows
Sep 16 14:32:19 Installed: djbdns-1.05-17.4.mr.el6.x86_64
Sep 16 14:45:18 Installed: djbdns-1.05-17.4.mr.el6.x86_64
Sep 16 15:02:08 Installed: djbdns-1.05-17.4.mr.el6.x86_64
Where did the log entry of yum uninstall of djbdns go?
And clearly bind isn't getting installed according to yum log. Also checked with yum list installed.
-
Ok, i found out that i had to
yum remove bind-utils bind-libs -y
and then i was able to switch back successfully to bind from djbns, but now the DNS server doesn't answer for any of the domains.
-
Now using DJBDNS i have big issues:
[root@mycloud ~]# dig mydomain.com @ns1.kloxoserver.com
;; reply from unexpected source: 111.151.111.85#53, expected 111.151.111.86#53
I've setup DNS server - ns1 and ns2.kloxoserver.com with IPs 111.151.111.86 and 111.151.111.87.
What's going on here? Why is Kloxo's main shared IPs (111.151.111.85) answering DNS queries?
@Mustafa all of our business is DOWN at the moment. Can you please help to get up again?
As i don't have a slave DNS, i need to get this up ASAP.
-
Why not try nsd. VPS for this forum using it.
-
Same problem with nsd too:
[root@mycloud ~]# dig mydomain.com @ns1.kloxoserver.com
;; reply from unexpected source: 111.151.111.85#53, expected 111.151.111.86#53
Reply from wrong IP why?
Update: Although i'm not sure, the problem looks like DNS server is binding to the control panels main shared IP, instead of just the IPs for ns1.kloxoserver.com and ns2.kloxoserver.com.
Cloud this be the problem?
-
Check your dns in intodns.com
-
ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
You should already know that your NS records at your nameservers are missing, so here it is again:
ns1.kloxoserver.com
ns2.kloxoserver.com.
I can ping both the name servers from any external records. Problem is within the Kloxo and that after the upgrade :(
It's totally broken now!
-
What is it mean?. http://whois.domaintools.com/kloxoserver.com
-
Please check PM for real domain name!
What is it mean?. http://whois.domaintools.com/kloxoserver.com
-
If you select djbdns or other, try 'yum remove bind*' and then 'sh /script/restart-dns'.
-
I tried that. Still same.
See PM pelase
-
Why doesn't /etc/named.conf not contain data from the Kloxo template? It's rather plain CentOS file from bind package.
I've earlier today tried to put the content /opt/configs/bind/etc/conf/named.conf into /etc/named.conf, but was unable to restart named.
Any idea why?
How can i at least go back to 6.5.1b which was working fine?
-
I've fixed the issue manually by using the Kloxo template file as the /etc/named.conf.
And there were some customer config that bind didn't like and i had to correct them.
Now all up and running.
Mustafa: For the future, please consider making such bigger changes in a new github branch and make a pull request (PR) so that we can test it for a while and you'll feedback from testers. That way we can avoid such downtime.
Our services were down over 8 hours today due to this! We are offering a cloud storage and have over 10k users.
-
don't mean to be funny here but why run a beta version for clients, surely you should be using the latest stable version?
Sure we all want the new features of version 7 but its not worth risking clients over it.
-
For developing Kloxo-MR 7, need information from users in this forum related to bug.
If you found an issue (let say dns server), why not try 'switch to another dns server' (let say 'bind' to 'nsd')?.