Date: Tue, 11 Jun 1996 01:03:16 +0200 (MET DST) From: Robert Eckardt <roberte@mep.ruhr-uni-bochum.de> To: garya@ics.com (Gary Aitken) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org Subject: Re: dns failure Message-ID: <199606102303.BAA21690@gluon.mep.ruhr-uni-bochum.de> In-Reply-To: <31BC655F.500F9F30@ics.com> from "Gary Aitken" at Jun 10, 96 12:11:44 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Gary,
> Can anyone give me some hints on what's going on?
I just read your mail about the named problem.
I have the same problem, also on a machine acting as a gateway.
I'm interested in any similarities/differences in your configuration
compared to mine.
(I haven't got any hint yet -- except for someone else also having the
same problem -- it seems, that it is not so rare.)
I don't understand, why named isn't using one of the forwarders ???
For completeness, I append my mail I sent last week to -hackers.
(Sorry, if you have it already)
Robert
8<---------------------------------------------------------------------------
Subject: named forgets how to resolve
Hi,
on one of our servers I have a serious problem with the name server.
(The machine is a Pentium/133 runnning 2.1-RELEASE from WC, serving
NFS for a few PCs and WWW and as a router -- so, no big load)
It has two ed-Interfaces.
Name: server.dekanat-bio.ruhr-uni-bochum.de
Addresses: 134.147.236.159, 134.147.133.33
After a few days it forgets how to resolve names. It can still reverse
resolve addresses.
The problem occured first after about 40 days uptime.
But now, a week and a reboot later, it happened again.
Noteably, the problems started always on Thursday, 2:00am o'clock
(/etc/daily ?).
foreach x ( messages* )
foreach? grep ns_req: / $x | head -3
foreach? end
messages:Jun 6 02:00:31 server named[70]: ns_req: no address for root server
messages:Jun 6 11:42:12 server named[70]: ns_req: no address for root server
messages:Jun 6 12:34:02 server named[70]: ns_req: no address for root server
messages.0:May 30 02:00:32 server named[70]: ns_req: no address for root server
messages.0:May 30 02:21:45 server named[70]: ns_req: no address for root server
messages.0:May 30 04:23:34 server named[70]: ns_req: no address for root server
I looked through the database at freefall.freebsd.org, and found a similar
case (Subject: Named goes wobbly after a while), but I don't see that the
solution (use current named.root, no syntax error in named.*, and refer to
existing hosts in SOA only) applies here.
I have to 'kill -TERM' and restart it to get it working again.
(for the next week ? :-)
A 'kill -HUP 70' gives with syslog at daemon.*:
Jun 6 22:30:29 server named[70]: reloading nameserver
Jun 6 22:30:29 server named[70]: Ready to answer queries.
Jun 6 22:30:29 server named[70]: USAGE 834093029 833648478 CPU=4.3792u/2.28068s CHILDCPU=0.010436u/0.010706s
Jun 6 22:30:29 server named[70]: NSTATS 834093029 833648478 A=408 NS=1 SOA=585 PTR=2172 MX=14 AXFR=2 ANY=1292
Jun 6 22:30:29 server named[70]: XSTATS 834093029 833648478 RQ=4474 RR=299 RIQ=0 RNXD=87 RFwdQ=225 RFwdR=225 RDupQ=0 RDupR=7 RFail=0 RFErr=0 RErr=0 RTCP=172 RA
XFR=2 RLame=0 ROpts=0 SSysQ=68 SAns=4083 SFwdQ=225 SFwdR=225 SDupQ=7 SFail=0 SFErr=0 SErr=0 RNotNsQ=4013 SNaAns=3114 SNXD=63
Jun 6 22:32:03 server named[70]: ns_req: no address for root server
Jun 6 22:34:48 server named[70]: sysquery: no addrs found for NS (G.ROOT-SERVERS.NET)
Jun 6 22:34:48 server named[70]: sysquery: no addrs found for NS (A.ROOT-SERVERS.NET)
Jun 6 22:34:48 server named[70]: sysquery: no addrs found for NS (H.ROOT-SERVERS.NET)
Jun 6 22:34:48 server named[70]: sysquery: no addrs found for NS (B.ROOT-SERVERS.NET)
Jun 6 22:34:48 server named[70]: sysquery: no addrs found for NS (C.ROOT-SERVERS.NET)
Jun 6 22:34:48 server named[70]: sysquery: no addrs found for NS (D.ROOT-SERVERS.NET)
Jun 6 22:34:48 server named[70]: sysquery: no addrs found for NS (E.ROOT-SERVERS.NET)
Jun 6 22:34:48 server named[70]: sysquery: no addrs found for NS (I.ROOT-SERVERS.NET)
Jun 6 22:34:48 server named[70]: sysquery: no addrs found for NS (F.ROOT-SERVERS.NET)
Jun 6 22:34:48 server named[70]: ns_req: no address for root server
[...]
8<--- /etc/named.boot: -------------------------------------------------------
; named.boot
directory /etc/named.d
; type domain source host/file backup file
primary dekanat-bio.ruhr-uni-bochum.de /etc/named.d/named.hosts
secondary 133.147.134.in-addr.arpa 134.147.32.40 /etc/named.d/named.rev
primary 0.0.127.in-addr.arpa /etc/named.d/named.local
cache . /etc/named.d/named.cache
forwarders 134.147.222.4 134.147.32.40
8<--- /etc/named.d/named.cache: ----------------------------------------------
[...]
; file named.root
;
; last update: Nov 8, 1995
; related version of root zone: 1995110800
;
;
; formerly NS.INTERNIC.NET
;
. 3600000 IN NS A.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
[...]
------------------------------------------------------------------------------
The server is subnetted 0xffffffe0 and gets its reverse address information
from the computer center (134.147.32.40), which maintains the database for the
134.147.133.0-subnet.
Any hints or requests to provide further information are welcome.
Thanks,
Robert
--
Robert Eckardt (
Ruhr-Universitaet Bochum, Inst.f.Theor.Physik, NB6/169 )
Universitaetsstrasse 150, D-44780 Bochum, Germany ----X---8----
Telefon: +49 234 700-3709, Telefax: +49 234 7094-574 8
E-Mail: RobertE@MEP.Ruhr-Uni-Bochum.de --------8----
URL: http://WWW.MEP.Ruhr-Uni-Bochum.de/
>>> Fuer die einen ist es bloss ein Betriebssystem, <<<
>>> fuer die anderen ist es der laengste Virus der Welt. .... Windows 95 <<<
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606102303.BAA21690>