From owner-freebsd-questions@FreeBSD.ORG Thu Jan 29 17:16:46 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 C911816A4CE for ; Thu, 29 Jan 2004 17:16:46 -0800 (PST) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5272B43D31 for ; Thu, 29 Jan 2004 17:16:45 -0800 (PST) (envelope-from mark@antsclimbtree.com) Received: (qmail 31000 invoked from network); 30 Jan 2004 01:16:44 -0000 Received: from lilbuddy.antsclimbtree.com ([216.27.183.129]) (envelope-sender )encrypted SMTP for ; 30 Jan 2004 01:16:44 -0000 Received: from adsl-66-122-112-170.dsl.snfc21.pacbell.net ([66.122.112.170] helo=[192.168.1.110]) by lilbuddy.antsclimbtree.com with asmtp (TLSv1:RC4-SHA:128) (Exim 4.30; FreeBSD) id 1AmNGu-0000BH-8R for questions@FreeBSD.ORG; Thu, 29 Jan 2004 17:16:36 -0800 Mime-Version: 1.0 (Apple Message framework v612) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: questions@FreeBSD.ORG From: Mark Edwards Date: Thu, 29 Jan 2004 17:16:40 -0800 X-Mailer: Apple Mail (2.612) X-Spam-Score: -4.9 (----) Subject: BIND 8.3 going insane on FreeBSD 4.9 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, 30 Jan 2004 01:16:46 -0000 So, I've seen this twice now. BIND completely flips its lid and utterly destroys the server. Logs say: 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.559 default: warning: sysquery: no addrs found for root NS (D.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (A.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (H.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (C.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.560 default: warning: sysquery: no addrs found for root NS (G.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (F.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (B.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.561 default: warning: sysquery: no addrs found for root NS (J.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (K.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (M.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (I.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.562 default: warning: sysquery: no addrs found for root NS (L.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (D.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (A.ROOT-SERVERS.NET) 29-Jan-2004 16:48:34.563 default: warning: sysquery: no addrs found for root NS (H.ROOT-SERVERS.NET) My root hints are up to date, and I've seen this both using forwarders and not. I've read that this is some incompatibility between BIND 8.3 and other servers. Is the only solution to this problem to run BIND 9? I really have to make sure this doesn't happen again, because it has catastrophic effects on the server. Thanks for any help!