From matt.hall@networkcorps.com  Fri Apr  4 13:31:02 2003
Return-Path: <matt.hall@networkcorps.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DF44D37B401
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  4 Apr 2003 13:31:01 -0800 (PST)
Received: from smtp800.mail.sc5.yahoo.com (smtp800.mail.sc5.yahoo.com [66.163.168.179])
	by mx1.FreeBSD.org (Postfix) with SMTP id 6555543FA3
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  4 Apr 2003 13:31:01 -0800 (PST)
	(envelope-from matt.hall@networkcorps.com)
Received: from adsl-67-124-30-44.dsl.lsan03.pacbell.net (HELO networkcorps.com) (hallm25@sbcglobal.net@67.124.30.44 with plain)
  by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 4 Apr 2003 21:31:01 -0000
Message-Id: <3E8DF997.8030301@networkcorps.com>
Date: Fri, 04 Apr 2003 13:31:03 -0800
From: Matt Hall <matt.hall@networkcorps.com>
To: FreeBSD-gnats-submit@freebsd.org
Subject: 4.7-4.8 BIND error (BIND goes haywire.)

>Number:         50612
>Category:       bin
>Synopsis:       4.7-4.8 BIND error (BIND goes haywire.)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Apr 04 13:40:01 PST 2003
>Closed-Date:    Sat Jul 12 23:45:41 PDT 2003
>Last-Modified:  Sat Jul 12 23:45:41 PDT 2003
>Originator:     angui.sh admin
>Release:        FreeBSD 4.8-RC i386
>Organization:
angui.sh admin
>Environment:
 System: FreeBSD tempest 4.8-RC FreeBSD 4.8-RC #25: Wed Mar 19 09:44:01 
 PST 2003 root@maelstrom:/usr/obj/usr/src/sys/ANGUISH.SMP i386
 
 
>Description:
 
 Occasionally BIND will simply go haywire - I have yet been able to
 accurately reproduce the problem. It will run fine for weeks, and
 then suddenly it will lock itself into some endless loop spewing
 this to syslog:
 
 Apr  3 16:07:21 tempest named[72288]: sysquery: no addrs found for root 
 NS (A.RO
 OT-SERVERS.NET)
 Apr  3 16:07:21 tempest named[72288]: sysquery: no addrs found for root 
 NS (C.RO
 OT-SERVERS.NET)
 Apr  3 16:07:21 tempest named[72288]: sysquery: no addrs found for root 
 NS (G.RO
 OT-SERVERS.NET)
 Apr  3 16:07:21 tempest named[72288]: sysquery: no addrs found for root 
 NS (F.RO
 OT-SERVERS.NET)
 Apr  3 16:07:21 tempest named[72288]: sysquery: no addrs found for root 
 NS (B.RO
 OT-SERVERS.NET)
 Apr  3 16:07:21 tempest named[72288]: sysquery: no addrs found for root 
 NS (J.RO
 OT-SERVERS.NET)
 
 I'm only using BIND as a local, caching nameserver for my NAT box and
 the machines behind it.
 
 My named.conf (with comments snipped):
 
 --- cut here ---
 
 options {
          directory "/etc/namedb";
          listen-on port 53 {
                  10.0.0.1;
                  127.0.0.1;
          };
          forward first;
          forwarders {
 		206.13.29.12;
 		206.13.30.12;
 		216.231.41.2;
 		216.231.41.22;
 		64.81.79.2;
          };
 };
 
 zone "." {
          type hint;
          file "named.root";
 };
 
 zone "0.0.127.in-addr.arpa" {
          type master;
          file "localhost.rev";
 };
 
 zone "internal" {
 	type master;
 	file "internal.fwd";
 };
 
 zone "0.0.10.in-addr.arpa" {
 	type master;
 	file "internal.rev";
 };
 
 
>How-To-Repeat:
 
 Random. My guesses are: My PPPoE connection drops or
 gets reset, and BIND, suddenly faced with no internet connection
 (horrors!) goes nutso, and never recovers despite the PPPoE connection
 coming back up. Hey, that was a good idea, let me try it now ... Nope.
 The other idea I have is that perhaps my Squid proxy which handles
 all port 80 traffic crossing my network (transparent proxying) might be
 hammering named for name lookups on large sites/multiple pages/images,
 but I can't verify or reproduce that either.
 
>Fix:
 
 	At this point, I have no choice but to kill/kill -9 named and
 restart the process (which is by then eating 70% of my dual CPU setup),
 wait for syslog to finish handling all the messages, and then things
 go back to normal, until the next time it goes haywire.
 
 If there is anything else I can record, look at, look into, to help
 track this down, please let me know.
 
 
 
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: ceri 
Responsible-Changed-When: Sat Apr 5 03:10:18 PST 2003 
Responsible-Changed-Why:  
Reassign misfiled PR. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=50612 
State-Changed-From-To: open->closed 
State-Changed-By: kris 
State-Changed-When: Sat Jul 12 23:45:22 PDT 2003 
State-Changed-Why:  
BIND is not maintained by FreeBSD.  Please take this up with 
the BIND developers instead. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=50612 
>Unformatted:
