From owner-freebsd-questions@FreeBSD.ORG Tue Sep 7 11:25:09 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 765DF16A4CE for ; Tue, 7 Sep 2004 11:25:09 +0000 (GMT) Received: from lv.raad.tartu.ee (lv.raad.tartu.ee [194.126.106.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F17C43D1F for ; Tue, 7 Sep 2004 11:25:08 +0000 (GMT) (envelope-from toomas.aas@raad.tartu.ee) Received: Message by Barricade lv.raad.tartu.ee with ESMTP id i87BP3qk005202; Tue, 7 Sep 2004 14:25:03 +0300 Message-Id: <200409071125.i87BP3qk005202@lv.raad.tartu.ee> Received: from INFO/SpoolDir by raad.tartu.ee (Mercury 1.48); 7 Sep 04 14:25:04 +0300 Received: from SpoolDir by INFO (Mercury 1.48); 7 Sep 04 14:24:44 +0300 From: "Toomas Aas" Organization: Tartu City Government To: Ion-Mihai Tetcu Date: Tue, 7 Sep 2004 14:24:37 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Priority: normal In-reply-to: <20040907130047.4334dc0e@it.buh.tecnik93.com> cc: 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 11:25:09 -0000 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) > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS (h.root-servers.net) > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS (f.root-servers.net) > Sep 7 12:57:45 it named[353]: sysquery: no addrs found for root NS (b.root-servers.net) > This problem plagued me for a long time on several FreeBSD 4 servers running BIND 8 from the base system. Google finds numerous discussions on this problem in various lists/newsgroups but a solution is rarely offered. Finally, I found someone's theory in a NetBSD (or was it OpenBSD) forum. I can't tell whether it is true or not, but it makes sense to me. If your BIND is configured to use a forwarder and this forwarder is really good then BIND (almost) never needs to contact the root servers. The root zone times out in memory and it is not reloaded from disk. It is only loaded when BIND is started. Thus, if your BIND finally needs to contact a root name server after a long time of getting all responses from forwarder, it turns out that the data for root zone is not available... Now, as I said, I cannot tell whether this theory is true or not. What I can say is that on all 4 machines where I run BIND I configured one of two workarounds: - use "forward only" so you *never* need to check the root zone - do not use forwarders at all so you check the root zone fairly frequently. I did this almost a year ago, and after that I never have had this problem again. HTH. -- Toomas Aas | toomas.aas@raad.tartu.ee | http://www.raad.tartu.ee/~toomas/ * Press any key to continue or any other key to quit.