From owner-freebsd-questions@FreeBSD.ORG Tue Sep 7 13:20:04 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99D6516A4CE; Tue, 7 Sep 2004 13:20:04 +0000 (GMT) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2C2243D3F; Tue, 7 Sep 2004 13:20:03 +0000 (GMT) (envelope-from itetcu@apropo.ro) Received: from it.buh.tecnik93.com (localhost.buh.tecnik93.com [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with SMTP id BA1B8195; Tue, 7 Sep 2004 16:19:56 +0300 (EEST) Date: Tue, 7 Sep 2004 16:19:55 +0300 From: Ion-Mihai Tetcu To: "Robert Eckardt" Message-ID: <20040907161955.2dbe797e@it.buh.tecnik93.com> In-Reply-To: <20040907122932.M26462@Robert-Eckardt.de> References: <20040907130047.4334dc0e@it.buh.tecnik93.com> <20040907130705.3d2636ac@it.buh.tecnik93.com> <20040907122932.M26462@Robert-Eckardt.de> X-Mailer: Sylpheed-Claws 0.9.12a (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: owner-freebsd-questions@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: named[353]: sysquery: no addrs found for root NS .......... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2004 13:20:04 -0000 On Tue, 7 Sep 2004 14:41:08 +0200 "Robert Eckardt" wrote: > 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 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. Kinda' funny since it has named.root handy. > 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.) Yes that what was happening here too; and that loop nice loaded the system. Thanks. BTW, 5.3 with debug.witness_watch=0 just rocks; the load is a half :) -- IOnut Unregistered ;) FreeBSD "user"