Dns Troubles

Z

zafar

Verified User
Joined
Apr 29, 2004
Messages
10
At first, DNS was working fine. Then after a few weeks of using the server, the domains stopped working. The pages wouldnt load and the named process wouldnt respond to stop/start/restart/reload commands. Then i ask for support here, and I was instructed to get a new Boot script, which i installed and restarted. DNS worked fine for another week but then it started having problems. Only the main domain name would work and the others wouldnt resolve, and then all domains wouldnt work, reguarless of restarting/reloading named. Then I restarted the whole server and it worked for about 14 hours. The domains stopped working and now the only one that works is http:// of the main domain (http://www. doesnt work) and no other domains work. The main domain is narutochaos.com and the ip is 69.30.195.3

Well, my friend made a script that kills Named and make sure its killed and then starts it up again, which im suppose to run when it messes up... which is ok for temporary use until its fixed
 
Last edited:
Hello,

That's something similar to what the boot script we provided does. (www.directadmin.com/named) The default script provided with the named rpm uses rndc, which doesn't seem to be very reliable.

What does your message log show for named restart/reload errors? You should be able to run

service named restart
service named reload

and not see any errors ("/usr/local/etc/rc.d/named restart" on FreeBSD)

John
 
logs

May 31 18:12:01 xeon named: named shutdown succeeded
May 31 18:12:01 xeon named[8688]: starting BIND 9.2.1 -u named
May 31 18:12:01 xeon named[8688]: using 4 CPUs
May 31 18:12:01 xeon named[8688]: loading configuration from '/etc/named.conf'
May 31 18:12:01 xeon named[8688]: no IPv6 interfaces found
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface lo, 127.0.0.1#53
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface eth0, 69.30.195.2#53
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface eth0:12, 69.30.195.16#53
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface eth0:0, 69.30.195.3#53
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface eth0:1, 69.30.195.4#53
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface eth0:2, 69.30.195.5#53
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface eth0:3, 69.30.195.6#53
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface eth0:4, 69.30.195.7#53
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface eth0:5, 69.30.195.8#53
May 31 18:12:01 xeon named[8688]: listening on IPv4 interface eth0:6, 69.30.195.9#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:7, 69.30.195.10#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:8, 69.30.195.11#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:9, 69.30.195.12#53
May 31 18:12:02 xeon named: named startup succeeded
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:10, 69.30.195.13#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:11, 69.30.195.14#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:13, 69.30.195.17#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:14, 69.30.195.18#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:15, 69.30.195.19#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:16, 69.30.195.20#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:17, 69.30.195.21#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:18, 69.30.195.22#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:19, 69.30.195.23#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:20, 69.30.195.24#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:21, 69.30.195.25#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:22, 69.30.195.26#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:23, 69.30.195.27#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:24, 69.30.195.28#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:25, 69.30.195.29#53
May 31 18:12:02 xeon named[8688]: listening on IPv4 interface eth0:26, 69.30.195.30#53
May 31 18:12:02 xeon named[8688]: command channel listening on 127.0.0.1#953
May 31 18:12:02 xeon named[8688]: zone 69.30.195.2/IN: loaded serial 2004042900
May 31 18:12:02 xeon named[8688]: zone 69.30.195.6/IN: loaded serial 2004052300
May 31 18:12:02 xeon named[8688]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
May 31 18:12:02 xeon named[8688]: zone anihaven.com/IN: loaded serial 2004050800
May 31 18:12:02 xeon named[8688]: zone animesearch.com/IN: loaded serial 2004050400
May 31 18:12:02 xeon named[8688]: zone artofanime.com/IN: loaded serial 2004042900
May 31 18:12:02 xeon named[8688]: zone fmachaos.com/IN: loaded serial 2004042900
May 31 18:12:02 xeon named[8688]: zone havenforums.com/IN: loaded serial 2004050200
May 31 18:12:02 xeon named[8688]: zone ionws.com/IN: loaded serial 2004053100
May 31 18:12:02 xeon named[8688]: zone lbmesa.com/IN: loaded serial 2004042900
May 31 18:12:02 xeon named[8688]: zone narutochaos.com/IN: loaded serial 2004050101
May 31 18:12:02 xeon named[8688]: zone development.narutochaos.com/IN: loaded serial 2004042900
May 31 18:12:02 xeon named[8688]: zone narutoguide.com/IN: loaded serial 2004050100
May 31 18:12:02 xeon named[8688]: zone teamnubz.com/IN: loaded serial 2004050900
May 31 18:12:02 xeon named[8688]: zone localhost/IN: loaded serial 42
May 31 18:12:02 xeon named[8688]: zone pianka.net/IN: loaded serial 2004052400
May 31 18:12:02 xeon named[8688]: zone addpower.org/IN: loaded serial 2004042900
May 31 18:12:02 xeon named[8688]: zone mattsplace.tk/IN: loaded serial 2004042900
May 31 18:12:02 xeon named[8688]: running
May 31 18:12:02 xeon named[8688]: zone ionws.com/IN: sending notifies (serial 2004053100)
May 31 18:12:02 xeon named[8688]: zone 69.30.195.2/IN: sending notifies (serial 2004042900)
May 31 18:12:02 xeon named[8688]: zone havenforums.com/IN: sending notifies (serial 2004050200)
May 31 18:12:02 xeon named[8688]: zone narutochaos.com/IN: sending notifies (serial 2004050101)
May 31 18:12:02 xeon named[8688]: zone anihaven.com/IN: sending notifies (serial 2004050800)
May 31 18:12:02 xeon named[8688]: zone fmachaos.com/IN: sending notifies (serial 2004042900)
May 31 18:12:02 xeon named[8688]: zone lbmesa.com/IN: sending notifies (serial 2004042900)
May 31 18:12:02 xeon named[8688]: zone narutoguide.com/IN: sending notifies (serial 2004050100)
May 31 18:12:02 xeon named[8688]: zone teamnubz.com/IN: sending notifies (serial 2004050900)
May 31 18:12:02 xeon named[8688]: zone addpower.org/IN: sending notifies (serial 2004042900)
May 31 18:12:02 xeon named[8688]: zone 69.30.195.6/IN: sending notifies (serial 2004052300)
May 31 18:12:02 xeon named[8688]: zone animesearch.com/IN: sending notifies (serial 2004050400)
May 31 18:12:02 xeon named[8688]: zone artofanime.com/IN: sending notifies (serial 2004042900)
May 31 18:12:02 xeon named[8688]: zone development.narutochaos.com/IN: sending notifies (serial 2004042900)
May 31 18:12:02 xeon named[8688]: zone pianka.net/IN: sending notifies (serial 2004052400)
May 31 18:12:03 xeon named[8688]: zone mattsplace.tk/IN: sending notifies (serial 2004042900)
May 31 18:12:04 xeon named[8688]: loading configuration from '/etc/named.conf'
May 31 18:12:04 xeon named[8688]: no IPv6 interfaces found
 
No, I'm not running a firewall.

Heres the result of Dig

[root@xeon root]# dig narutochaos.com @localhost

; <<>> DiG 9.2.1 <<>> narutochaos.com @localhost
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20568
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;narutochaos.com. IN A

;; ANSWER SECTION:
narutochaos.com. 14400 IN A 69.30.195.3

;; AUTHORITY SECTION:
narutochaos.com. 14400 IN NS ns1.narutochaos.com.
narutochaos.com. 14400 IN NS ns2.narutochaos.com.

;; ADDITIONAL SECTION:
ns1.narutochaos.com. 14400 IN A 69.30.195.4
ns2.narutochaos.com. 14400 IN A 69.30.195.5

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(localhost)
;; WHEN: Tue Jun 1 13:52:40 2004
;; MSG SIZE rcvd: 117
 
You must log in or register to reply here.
Back
Top