Date: Tue, 7 Sep 2004 14:41:08 +0200 From: "Robert Eckardt" <Robert.Eckardt@Robert-Eckardt.de> To: Ion-Mihai Tetcu <itetcu@apropo.ro> Cc: freebsd-questions@freebsd.org Subject: Re: named[353]: sysquery: no addrs found for root NS .......... Message-ID: <20040907122932.M26462@Robert-Eckardt.de> In-Reply-To: <20040907130705.3d2636ac@it.buh.tecnik93.com> References: <20040907130047.4334dc0e@it.buh.tecnik93.com> <20040907130705.3d2636ac@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 7 Sep 2004 13:07:05 +0300, Ion-Mihai Tetcu wrote > On Tue, 7 Sep 2004 13:00:47 +0300 > Ion-Mihai Tetcu <itetcu@apropo.ro> wrote: > > > Hi, > > > > > > From time to time I get this: > > > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS (d.root-servers.net) > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS (a.root-servers.net) > > Sep 7 12:57:44 it named[353]: sysquery: no addrs found for root NS (c.root-servers.net) Hi, I had the same problem a while ago. I had configured my ISP's name-server (actually several of them) to forward requests to. It happened that one of them became unreachable. >From (just quickly) looking at the source, I found that named ends in this very loop as it does not try to actually request adresses for the root name-servers but rather writes out error messages. The funny thing was that the forwarders are managed in the same list as the root servers. After removing any forwarders from my named-config and relying completely on the root servers I never had the problem again. (Before this it happend after a few hours up to several weeks of named's run-time.) Regards, Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040907122932.M26462>