From owner-freebsd-net@FreeBSD.ORG  Sat Mar  4 19:13:23 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 8431916A420
	for <freebsd-net@freebsd.org>; Sat,  4 Mar 2006 19:13:23 +0000 (GMT)
	(envelope-from yar@comp.chem.msu.su)
Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D7A2743D7F
	for <freebsd-net@freebsd.org>; Sat,  4 Mar 2006 19:13:19 +0000 (GMT)
	(envelope-from yar@comp.chem.msu.su)
Received: from comp.chem.msu.su (localhost [127.0.0.1])
	by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id k24JD7JY001017
	for <freebsd-net@freebsd.org>; Sat, 4 Mar 2006 22:13:07 +0300 (MSK)
	(envelope-from yar@comp.chem.msu.su)
Received: (from yar@localhost)
	by comp.chem.msu.su (8.13.4/8.13.3/Submit) id k24JD7Av001016
	for freebsd-net@freebsd.org; Sat, 4 Mar 2006 22:13:07 +0300 (MSK)
	(envelope-from yar)
Date: Sat, 4 Mar 2006 22:13:06 +0300
From: Yar Tikhiy <yar@comp.chem.msu.su>
To: freebsd-net@freebsd.org
Message-ID: <20060304191306.GA600@comp.chem.msu.su>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Subject: BIND incompatibility
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Mar 2006 19:13:23 -0000

Hi there,

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 :-)

-- 
Yar