From owner-freebsd-questions@FreeBSD.ORG Thu Feb 19 23:35:55 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 221BE16A4CE for ; Thu, 19 Feb 2004 23:35:55 -0800 (PST) Received: from mail001.syd.optusnet.com.au (mail001.syd.optusnet.com.au [211.29.132.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43A8E43D1D for ; Thu, 19 Feb 2004 23:35:54 -0800 (PST) (envelope-from tfrank@optushome.com.au) Received: from marvin.home.local (c211-28-241-189.eburwd5.vic.optusnet.com.au [211.28.241.189])i1K7Zpr28105; Fri, 20 Feb 2004 18:35:52 +1100 Received: by marvin.home.local (Postfix, from userid 1001) id 4E8011B8; Fri, 20 Feb 2004 18:35:51 +1100 (EST) Date: Fri, 20 Feb 2004 18:35:51 +1100 From: Tony Frank To: John Message-ID: <20040220073551.GA97843@marvin.home.local> References: <20040219222504.A95569@starfire.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040219222504.A95569@starfire.mn.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org Subject: Re: endless "sysquery: no addrs found for root" 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: Fri, 20 Feb 2004 07:35:55 -0000 Hi, On Thu, Feb 19, 2004 at 10:25:04PM -0600, John wrote: > OK. I'm stumped. Hopefully we can help. > This is on a FreeBSD 4.9-STABLE system with named 8.3.7-REL Fairly standard setup. tony@marvin [119]:/usr/src> uname -a FreeBSD marvin.home.local 4.9-STABLE FreeBSD 4.9-STABLE #122: Fri Jan 23 08:52:48 EST 2004 root@:/data/ad3/obj/usr/src/sys/MARVIN i386 Fri Feb 20 18:26:15 EST 2004 tony@marvin [120]:/usr/src> named -v named 8.3.7-REL Fri Jan 23 17:43:07 EST 2004 tony@marvin.home.local:/data/ad3/obj/usr/src/usr.sbin/named > I have set up a pretty basic named.conf file: > > options { > directory "/etc/namedb"; > > forwarders { > 64.81.159.2; > 216.231.41.2; > }; > > zone "." { > type hint; > file "named.root"; > }; > > zone "0.0.127.IN-ADDR.ARPA" { > type master; > file "localhost.rev"; > }; > > zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" { > type master; > file "localhost-v6.rev"; > }; > > When I try to start named with this config, the log file shows > Feb 19 22:16:50 jsrh named[177]: starting (/etc/namedb/named.conf). named 8.3.7-REL Tue Feb 17 15:01:48 CST 2004 john@dexter.starfire.mn.org:/usr/obj/usr/src/usr.sbin/named > Feb 19 22:16:50 jsrh named[178]: Ready to answer queries. > > but then I get an endless stream of > Feb 19 22:16:58 jsrh named[178]: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET) > > for each one of the root name servers. Just for grins, I downloaded the > lastest named.root file, but that didn't help (of course). I also dropped > the firewall, but that didn't help, either. > > When I run nslookup with the name nameservers listed as in the forwarders, > I'm able to make queries from this same system, including resolving > the root NS entries that are generating all these errors. > > I'm clearly assuming something I shouldn't, or think I know something I > don't - because this just doesn't make sense to me. fyi I do not get this kind of error, but then I have "forward-only" configured in my options section to send all queries to my ISP DNS servers instead of querying root servers direct. See below. log messages at startup: %%%% Feb 19 17:39:48 marvin named[28890]: starting (/etc/namedb/named.conf). named 8.3.7-REL Fri Jan 23 17:43:07 EST 2004 tony@marvin.home.local:/data/ad3/obj/usr/src/usr.sbin/named Feb 19 17:39:49 marvin named[28890]: limit files set to fdlimit (1024) Feb 19 17:39:49 marvin named[28890]: hint zone "" (IN) loaded (serial 0) Feb 19 17:39:49 marvin named[28890]: master zone "0.0.127.IN-ADDR.ARPA" (IN) loaded (serial 20020407) Feb 19 17:39:49 marvin named[28890]: master zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA" (IN) loaded (serial 20020407) Feb 19 17:39:49 marvin named[28890]: master zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" (IN) loaded (serial 20020407) Feb 19 17:39:49 marvin named[28890]: master zone "home.local" (IN) loaded (serial 2004021902) Feb 19 17:39:49 marvin named[28890]: master zone "168.192.in-addr.arpa" (IN) loaded (serial 2004021902) Feb 19 17:39:49 marvin named[28890]: listening on [192.168.3.2].53 (fxp0) Feb 19 17:39:49 marvin named[28890]: listening on [127.0.0.1].53 (lo0) Feb 19 17:39:49 marvin named[28890]: Forwarding source address is [0.0.0.0].53 Feb 19 17:39:49 marvin named[28891]: Ready to answer queries. %%%% The only subsequent messages I get (hourly) are: %%%% Feb 20 07:39:49 marvin named[28891]: Cleaned cache of 8 RRsets Feb 20 08:39:49 marvin named[28891]: Cleaned cache of 2 RRsets Feb 20 09:39:49 marvin named[28891]: Cleaned cache of 5 RRsets %%%% The named.root I have is the stock file installed by FreeBSD: ; $FreeBSD: src/etc/namedb/named.root,v 1.9.2.1 2002/11/06 09:24:12 dougb Exp $ For reference, my named.conf is: %%%% acl allowed_sources { localhost; localnets; }; options { directory "/etc/namedb"; forward only; forwarders { 198.142.0.66; // dns01.meb.optusnet.com.au 203.2.75.108; // dns01.syd.optusnet.com.au 211.29.132.154; // dns07.syd.optusnet.com.au }; query-source address * port 53; listen-on port 53 { 127.0.0.1; 192.168.3.2; }; allow-query { allowed_sources; }; }; key DHCP_UPDATER { algorithm HMAC-MD5.SIG-ALG.REG.INT; secret ****** ; }; zone "." { type hint; file "named.root"; }; zone "0.0.127.IN-ADDR.ARPA" { type master; file "localhost.rev"; }; zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA" { type master; file "localhost-v6.rev"; }; zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" { type master; file "localhost-v6.rev"; }; zone "home.local" { type master; notify no; file "p/home.local"; allow-update { key DHCP_UPDATER; }; allow-transfer { 192.168.3.5; }; }; zone "168.192.in-addr.arpa" { type master; notify no; file "p/168.192.in-addr.arpa"; allow-update { key DHCP_UPDATER; }; allow-transfer { 192.168.3.5; }; }; %%%% Regards, Tony