Bug 50612

Summary: 4.7-4.8 BIND error (BIND goes haywire.)
Product: Base System Reporter: Matt Hall <matt.hall>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Matt Hall 2003-04-04 22:40:01 UTC
 
 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";
 };

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.
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.
Comment 1 Ceri Davies freebsd_committer freebsd_triage 2003-04-05 12:10:18 UTC
Responsible Changed
From-To: gnats-admin->freebsd-bugs

Reassign misfiled PR.
Comment 2 Kris Kennaway freebsd_committer freebsd_triage 2003-07-13 07:45:22 UTC
State Changed
From-To: open->closed

BIND is not maintained by FreeBSD.  Please take this up with 
the BIND developers instead.