From owner-freebsd-questions@FreeBSD.ORG Thu Feb 19 20:25:06 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 388FE16A4CE for ; Thu, 19 Feb 2004 20:25:06 -0800 (PST) Received: from dexter.starfire.mn.org (starfire.skypoint.net [66.93.17.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9CEB43D1D for ; Thu, 19 Feb 2004 20:25:05 -0800 (PST) (envelope-from john@dexter.starfire.mn.org) Received: (from john@localhost) by dexter.starfire.mn.org (8.11.3/8.11.3) id i1K4P4B97150 for freebsd-questions@freebsd.org; Thu, 19 Feb 2004 22:25:04 -0600 (CST) (envelope-from john) Date: Thu, 19 Feb 2004 22:25:04 -0600 From: John To: freebsd-questions@freebsd.org Message-ID: <20040219222504.A95569@starfire.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: 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 04:25:06 -0000 OK. I'm stumped. This is on a FreeBSD 4.9-STABLE system with named 8.3.7-REL 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. Help? TIA -- John Lind john@starfire.MN.ORG