bug in bind-9.3.2-P2 - SERVFAIL?

Wes Rogers wrogers at gmail.com
Wed Aug 22 13:54:09 UTC 2007


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?

20-Aug-2007 15:41:35.930 unexpected RCODE (SERVFAIL) resolving
'example.com/A/IN': 1.2.3.4#53
20-Aug-2007 16:54:15.393 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53
20-Aug-2007 16:57:29.681 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53
20-Aug-2007 16:58:16.835 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53
20-Aug-2007 16:59:07.179 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53
20-Aug-2007 16:59:54.423 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53
20-Aug-2007 17:00:40.484 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53
20-Aug-2007 17:17:56.432 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53
20-Aug-2007 17:22:54.679 unexpected RCODE (SERVFAIL) resolving
'example.com/NS/IN': 1.2.3.4#53
20-Aug-2007 17:25:26.703 unexpected RCODE (SERVFAIL) resolving
'example.com/NS/IN': 1.2.3.4#53
20-Aug-2007 17:26:06.944 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53
20-Aug-2007 17:27:15.254 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53
20-Aug-2007 17:34:11.671 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/NS/IN': 1.2.3.4#53
20-Aug-2007 17:46:44.871 unexpected RCODE (SERVFAIL) resolving
'ftp.example.com/A/IN': 1.2.3.4#53

Thanks,
Wes



More information about the bind-users mailing list