From owner-freebsd-questions@FreeBSD.ORG Wed Sep 8 22:36:51 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 0B6CA16A4CE for ; Wed, 8 Sep 2004 22:36:51 +0000 (GMT) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id C691F43D45 for ; Wed, 8 Sep 2004 22:36:49 +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 C35313B5; Wed, 8 Sep 2004 15:11:06 +0300 (EEST) Date: Wed, 8 Sep 2004 15:11:05 +0300 From: Ion-Mihai Tetcu To: horio shoichi Message-ID: <20040908151105.7029c6fc@it.buh.tecnik93.com> In-Reply-To: <20040907.222811.d3edc1276d5892bc.10.0.3.20@bugsgrief.net> References: <20040907130047.4334dc0e@it.buh.tecnik93.com> <200409071125.i87BP3qk005202@lv.raad.tartu.ee> <20040907.222811.d3edc1276d5892bc.10.0.3.20@bugsgrief.net> 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: 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: Wed, 08 Sep 2004 22:36:51 -0000 On Wed, 8 Sep 2004 07:28:11 +0900 horio shoichi wrote: > On Tue, 7 Sep 2004 14:24:37 +0300 > "Toomas Aas" 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) > > > 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. > > Hmm, then the easiest cure against OP's would be > periodically (say, per week) requesting purposely > wrong request (e.g., nslookup example.heh) ? Actually the uptime was 3 days (I've upgraded to 5.3B3) and I'm _sure_ to have entered some non-existent addresses in my web browser. -- IOnut Unregistered ;) FreeBSD "user" 5.3-BETA3 - try `sysctl debug.witness_watch=0` and prepare to fly :-)