DNS Issue - Lame NS and BIND Problem

KonokoHost

Member
Mar 25, 2003
17
0
151
Chino Hills, CA
Attempting to restart named
Waiting for named to restart.... . . . . . . . . . . finished.

named status

named 1480 0.7 0.6 29976 3016 ? S 12:39 0:00 /usr/sbin/named -u named


named started ok Aug 8 12:39:42 chills named[6550]: shutting down: flushing changes Aug 8 12:39:42 chills named[6550]: stopping command channel on 127.0.0.1#953 Aug 8 12:39:42 chills named[6550]: no longer listening on 127.0.0.1#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.81.18#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.2#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.3#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.4#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.5#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.6#53 Aug 8 12:39:42 chills named[6550]: exiting Aug 8 12:39:42 chills named[1480]: starting BIND 9.2.1 -u named Aug 8 12:39:42 chills named[1480]: using 1 CPU Aug 8 12:39:42 chills named[1480]: loading configuration from '/etc/named.conf' Aug 8 12:39:42 chills named: named startup succeeded Aug 8 12:39:42 chills named[1480]: no IPv6 interfaces found Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface eth0, 66.90.81.18#53 Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface eth0:1, 66.90.77.2#53 Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface eth0:2, 66.90.77.3#53 Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface eth0:3, 66.90.77.4#53 Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface eth0:4, 66.90.77.5#53 Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface eth0:5, 66.90.77.6#53 Aug 8 12:39:42 chills named[1480]: command channel listening on 127.0.0.1#953 Aug 8 12:39:42 chills named[1480]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 Aug 8 12:39:42 chills named[1480]: zone aznxtc69.com/IN: loaded serial 2004062001 Aug 8 12:39:42 chills named[1480]: zone REMOVED.com/IN: loaded serial 2004062001 Aug 8 12:39:42 chills named[1480]: zone REMOVED.com/IN: loaded serial 2004062001 Aug 8 12:39:42 chills named[1480]: zone REMOVED.com/IN: loaded serial 2004062001 Aug 8 12:39:42 chills named[1480]: zone REMOVED.com/IN: loaded serial 2004072801 Aug 8 12:39:42 chills named[1480]: zone REMOVED.com/IN: loaded serial 2004062001 Aug 8 12:39:42 chills

I'm a noob at DNS stuff, so I need someones help. Theres about 40 more lines of that zone loaded stuff, then we get this...

expired Aug 8 12:39:42 chills named[1480]: zone www.REMOVED.net/IN: sending notifies (serial 2004042500) Aug 8 12:39:42 chills named[1480]: zone www.REMOVED.com/IN: sending notifies (serial 2004050301) Aug 8 12:39:42 chills named[1480]: zone REMOVED.com/IN: sending notifies (serial 2004071801) Aug 8 12:39:42 chills named[1480]: zone REMOVED.com/IN: expired Aug 8 12:39:42 chills named[1480]: zone REMOVED.com/IN: expired Aug 8 12:39:42 chills named[1480]: zone REMOVED.net/IN: expired

I get that for every singled domain on the server except feelthefusion.org (which is the upper level of the hostname, chills.feelthefusion.org).

No sites will load and I get lame Nameserver errors on DNS Reports.com
Much googling and searching at WHT hasn't helped me.

Cash reward if you can help,
thankyou.
-randyc
 

KonokoHost

Member
Mar 25, 2003
17
0
151
Chino Hills, CA
zone "fakedomain.com" {
type slave;
masters {
66.98.218.80;
};
file "/var/named/fakedomain.com.db";
};


theres one of the zones, I changed the domain to fakedomain.com instead of the real domain of course.
 

sawbuck

Well-Known Member
Jan 18, 2004
1,365
9
168
cPanel Access Level
Root Administrator
Dns report for feelthefusion.org looks good as do the ns1&ns2.feelthefusion.org name servers.
My guess is a problem with the httpd.conf. Have you changed anything recently with your setup? Posting or sending a PM with some non working domain info might be useful also.
 

theprimehost

Active Member
Nov 24, 2002
29
0
151
I'm getting similar results and no changes have been made as of yet.
 

theprimehost

Active Member
Nov 24, 2002
29
0
151
I've also tried rolling back to previous versions of named.conf and httpd.conf and neither seems to have corrected the problem.
 

SirConfucious

Member
Oct 21, 2003
5
0
151
if these are slaved domains, you should show us a copy of one of the generated files. If these are masters, show us the zone file. From the logs, it's odd that it's trying to load www.REMOVED.com as a zone, as it should be an A record, not a zone.
 

KonokoHost

Member
Mar 25, 2003
17
0
151
Chino Hills, CA
I'm still learning bout when it comes to DNS,

whats the difference between slave and masters?

Just today it stopped working after my little fix*

After my little fix*, I now have a named.conf that looks like this...


zone "DOMAINONE.net" {
type slave;
masters {
66.98.81.18;
};
file "/var/named/DOMAINONE.net.db";
};

zone "DOMAINTWO.com" {
type slave;
masters {
66.98.81.18;
};
file "/var/named/DOMAINTWO.com.db";
};

and the file starts off with....

key "rndckey" {
algorithm hmac-md5;
secret "B REMOVED 7gZ8UBTMTHg==";
};


controls {
inet 127.0.0.1 allow { localhost; } keys { "rndckey"; };
};







options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
zone "." IN {
type hint;
file "/var/named/named.ca";
};

zone "0.0.127.in-addr.arpa" IN {
type slave;
masters {
66.98.81.18;
};
file "/var/named/named.local";
};


*my little fix: I noticed the IPs were all wrong, so I fixed them to what the servers IP's were, but that only worked till this morning.
 

knipper

Well-Known Member
Sep 4, 2001
107
0
316
I just wanted to chime in here as well....

Just a couple days ago I noticed something similar when I restart bind.
I am also getting the...
named started ok Aug 8 12:39:42 chills named[6550]: shutting down: flushing changes Aug 8 12:39:42 chills named[6550]: stopping command channel on 127.0.0.1#953 Aug 8 12:39:42 chills named[6550]: no longer listening on 127.0.0.1#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.81.18#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.2#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.3#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.4#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.5#53 Aug 8 12:39:42 chills named[6550]: no longer listening on 66.90.77.6#53 Aug 8 12:39:42 chills named[6550]: exiting Aug 8 12:39:42 chills named[1480]: starting BIND 9.2.1 -u named Aug 8 12:39:42 chills named[1480]: using 1 CPU Aug 8 12:39:42 chills named[1480]: loading configuration from '/etc/named.conf' Aug 8 12:39:42 chills named: named startup succeeded Aug 8 12:39:42 chills named[1480]: no IPv6 interfaces found Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface eth0, 66.90.81.18#53 Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface eth0:1, 66.90.77.2#53 Aug 8 12:39:42 chills named[1480]: listening on IPv4 interface eth0:2, 66.90.77.3#53 Aug 8 12:39:42 chills named[1480]:
which I had never seen before. (3+ years on cPanel)

However unlike KonokoHost I do not get the nameserver problems, or any errors on DNSReports.com

So is cpanel now just showing the output of bind when restarting... when it never did before?
 

raed

Registered
Apr 1, 2004
1
0
151
named started ok Jun 14 17:34:40 usaal named[14475]: shutting down: flushing changes Jun 14 17:34:40 usaalnamed[14475]: stopping command channel on 127.0.0.1#953 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on 127.0.0.1#53 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on ###.###.###.####53 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on ###.###.###.####53 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on ###.###.###.####53 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on 66.45.237.229#53 Jun 14 17:34:40 sham named[14475]: no longer listening on 66.45.237.230#53 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on ###.###.###.##53 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on ###.###.###.###53 Jun 14 17:34:40 usaal named[14475]: no longer listening on ###.###.###.###53 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on ###.###.###.###53 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on ###.###.###.###53 Jun 14 17:34:40 usaalnamed: succeeded Jun 14 17:34:40 usaalnamed[14475]: no longer listening on ###.###.###.####53 Jun 14 17:34:40 usaalnamed[14475]: no longer listening on ###.###.###.####53 Jun 14 17:34:40 usaalnamed[14475]: no longer
:confused: me too (same proplem for 3 server ) pleas help :(