Frequent ndc restart needed

MeltDown meltdown at thirdtower.com
Wed Jun 14 23:04:53 UTC 2000


Hi!

I'm having a lot of trouble with my bind. Everything runs smoothly, except 
that every now and then I have to restart named. "Every now and then" can 
vary from twice a minute to once every two days. I have to restart named 
because at some point it will simply refuse to look up any address. It 
keeps accepting connections, it just returns a "DNS unknown" like message. 
It doesn't segfault or something.

Currently we (the people on my LAN) have a single nameserver, which serves 
both our internal and our external addresses. I know, it would be better to 
separate the internal from the external, and we'll do that soon, because 
we'll get us a second server.

Named also complains a lot about lame servers. Below is a snippet from the 
logs.

I hope you can help me. Restarting named is getting really annoying.

Greetz,
MeltDown


Server config:
P90, 32 Mb EDO-Ram, 4 Gb harddisk, ADSL internet connection

Log snippet:

(every line starts with "Jun 15 00:36:41 acer named[30325]", but I took 
that away for clarity)

starting.  named 8.2.2-P5 Mon Feb 28 10:17:53 EST 2000
hint zone "" (IN) loaded (serial 0)
master zone "0.0.127.IN-ADDR.ARPA" (IN) loaded (serial 200006120)
master zone "thirdtower.com" (IN) loaded (serial 200006121)
master zone "thirdtower.demon.nl" (IN) loaded (serial 200006121)
master zone "10.IN-ADDR.ARPA" (IN) loaded (serial 200006121)
listening on [127.0.0.1].53 (lo)
listening on [10.1.0.2].53 (eth0)
listening on [10.0.2.3].53 (eth1)
listening on [10.0.3.1].53 (eth1:0)
listening on [10.0.3.2].53 (eth1:1)
listening on [10.0.3.3].53 (eth1:2)
listening on [10.0.3.4].53 (eth1:3)
listening on [10.0.3.5].53 (eth1:4)
listening on [10.67.195.129].53 (ppp0)
listening on [194.109.221.152].53 (ppp0:0)
listening on [212.238.13.43].53 (ppp1)
Forwarding source address is [0.0.0.0].2344
Ready to answer queries.
ns_forw: sendto([202.12.27.33].53): Network is unreachable
Lame server on '' (in ''?): [192.203.230.10].53 'E.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [192.112.36.4].53 'G.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [198.41.0.10].53 'J.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [198.41.0.4].53 'A.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [128.63.2.53].53 'H.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [128.9.0.107].53 'B.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [198.32.64.12].53 'L.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [202.12.27.33].53 'M.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [193.0.14.129].53 'K.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [192.36.148.17].53 'I.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [128.8.10.90].53 'D.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [192.33.4.12].53 'C.ROOT-SERVERS.NET'
Lame server on '' (in ''?): [192.5.5.241].53 'F.ROOT-SERVERS.NET'
ns_forw: query(51.13.188.62.in-addr.arpa) All possible A RR's lame
ns_resp: query(wwp.mirabilis.com) All possible A RR's lame
"thirdtower.com IN MX" points to a CNAME (mail.thirdtower.com)
sysquery: query(name.iad.gblx.net) All possible A RR's lame
sysquery: query(DNS-02.ICQ.NET) All possible A RR's lame




More information about the bind-users mailing list