bug in bind-9.3.2-P2 - SERVFAIL?

Mark Andrews Mark_Andrews at isc.org
Wed Aug 22 22:17:04 UTC 2007


> On 8/22/07, Wes Rogers <wrogers at gmail.com> wrote:
> > Situation :
> >
> > (external zone managed somewhere else on inet)
> > ns1.example.com - responds with records
> > ns2.example.com - responds with SERVFAIL
> > ns3.example.com - does not respond
> >
> > Our internal bind-9.3.2-P2 servers insist on querying ns2.example.com
> > it appears, and are quiting on SERVFAIL instead of trying the next
> > server - networking is fine. A dig +trace always works from our
> > internal dns servers. Could this be a possible bug in bind-9.3.2-P2?

	named does go onto the next server.

> > 20-Aug-2007 15:41:35.930 unexpected RCODE (SERVFAIL) resolving
> > 'example.com/A/IN': 1.2.3.4#53
> 
> I have reproduced this problem on BIND 9.4.1-P1
> 
> It appears to only affect BIND when views are enabled.  There is one
> authoritative server out of the three that is responding with valid
> records as Wes indicated.

	I suspect that you are talking to the wrong view on ns2.example.com
	or one of the views on ns2.example.com doesn't have the zone loaded.
	You need to work out why ns2.example.com is returniong SERVFAIL.
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org



More information about the bind-users mailing list