From owner-freebsd-net@FreeBSD.ORG Sun Mar 5 06:29:07 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4750B16A420 for ; Sun, 5 Mar 2006 06:29:07 +0000 (GMT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B42043D46 for ; Sun, 5 Mar 2006 06:29:06 +0000 (GMT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.3/8.13.3) with ESMTP id k256Sd23070086; Sun, 5 Mar 2006 13:28:39 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.3/8.13.3/Submit) id k256SdeA070085; Sun, 5 Mar 2006 13:28:39 +0700 (KRAT) (envelope-from eugen) Date: Sun, 5 Mar 2006 13:28:39 +0700 From: Eugene Grosbein To: Yar Tikhiy Message-ID: <20060305062839.GA69680@svzserv.kemerovo.su> References: <20060304191306.GA600@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060304191306.GA600@comp.chem.msu.su> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: Re: BIND incompatibility X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Mar 2006 06:29:07 -0000 On Sat, Mar 04, 2006 at 10:13:06PM +0300, Yar Tikhiy wrote: > Just want to remind about a problem I've finally run into myself. > There has been a lot of gossip on it, but next to no tech details. > Namely, BIND8 will go nuts and spit out tons of error messages per > second if its forwarder happens to be BIND9 and "forwarders only" > is not in effect. The error message reads: > > sysquery: no addrs found for root NS > > I saw that after two my DNS servers had been upgraded today along > their respective branches, 4-STABLE and 6-STABLE, which had involved > no changes to named.conf or named.root. > > Has anybody got links to tech details why the trouble happens? > Sorry, today I had little time for debugging and tcpdumping, just > had to make sure it all worked by the end of the day :-) This happens to me several times per year. The following script works around the probem when it comes. /etc/syslog.conf feeds it with named's logs: #!/bin/sh fgrep 'sysquery: no addrs found for root NS' | while read line do killall -9 named sleep 1 /usr/sbin/named -u bind -g bind echo $line | mail -s "named restarted" root sleep 29 exit 0 done