Date: Sat, 23 Nov 1996 20:41:05 +0100 (MET) From: Robert Eckardt <roberte@mep.ruhr-uni-bochum.de> To: questions@freebsd.org Subject: named problems (again) Message-ID: <199611231941.UAA03396@ghost.mep.ruhr-uni-bochum.de>
next in thread | raw e-mail | index | archive | help
Hi all ! A few months ago I reported problems with the name daemon on a 2.1.0-R machine. But -- except from someone having the same problem -- I got no answer. I know that it is difficult to reproduce. However, I think it would be nice to find out whether I did a configuration error or there is a bug in named. Therefore, I will let named in this state for the time being. It started today at 19:19. Nov 23 19:19:30 server named[68]: ns_req: no address for root server Nov 23 19:19:30 server named[68]: ns_req: no address for root server [..] Nov 23 19:53:07 server named[68]: ns_req: no address for root server Nov 23 19:53:16 server last message repeated 3 times Nov 23 20:07:48 server named[68]: ns_req: no address for root server 20:13 server: /root 0#% uptime 8:14PM up 10 days, 19:05, 1 user, load averages: 0.00, 0.00, 0.00 It serves as: primary dekanat-bio.ruhr-uni-bochum.de named.hosts secondary 133.147.134.in-addr.arpa 134.147.32.40 named.rev [..] forwarders 134.147.222.4 134.147.32.40 As an example a few working and non-working requests: 20:14 server: /root 0#% nslookup gluon.mep.ruhr-uni-bochum.de Server: server.dekanat-bio.ruhr-uni-bochum.de Address: 134.147.133.33 *** server.dekanat-bio.ruhr-uni-bochum.de can't find gluon.mep.ruhr-uni-bochum.de: Server failed 20:15 server: /root 0#% nslookup gluon.mep.ruhr-uni-bochum.de 134.147.32.40 Server: ns1.ruhr-uni-bochum.de Address: 134.147.32.40 Name: gluon.mep.ruhr-uni-bochum.de Addresses: 134.147.6.1, 134.147.160.165 20:15 server: /root 0#% nslookup 134.147.32.40 Server: server.dekanat-bio.ruhr-uni-bochum.de Address: 134.147.133.33 *** server.dekanat-bio.ruhr-uni-bochum.de can't find 134.147.32.40: Server failed 20:16 server: /root 0#% nslookup ns1.ruhr-uni-bochum.de Server: server.dekanat-bio.ruhr-uni-bochum.de Address: 134.147.133.33 Non-authoritative answer: Name: ns1.ruhr-uni-bochum.de Address: 134.147.32.40 It seems to be a problem with cache inconsistencies and the update intervalls of this and the primary server for the 133.147.134.in-addr.arpa domain in the computer center. May be someone can give me a hint what to try to locate the cause and/or to fix it. (The problem goes away when I kill and restart the daemon. reload does not help.) Nov 13 01:09:27 server named[67]: starting. named LOCAL-951116.090057 Thu Nov 16 09:00:57 1995 jkh@westhill.cdrom.com:/usr/src/usr.sbin/named Thanks, Robert -- Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611231941.UAA03396>