Hi Folks,
We are testing BIND 9.4.0b2 in various production locations on
our network. One issue we've noticed is that BIND (as a recursive) is
considering some servers lame, even though they are answering perfectly
for thier zone.

Application example: Querying the relays.ordb.org zone for open relay
information. Our mail server will execute a number of DNS requests for
hosts within relays.ordb.org to this instance of BIND. When reviewing the
log, we see:

Oct 17 17:47:29 mxin2 named[750]: lame server resolving
'91.249.13.204.relays.ordb.org' (in 'relays.ordb.org'?): 206.154.202.54#53
Oct 17 17:47:29 mxin2 named[750]: lame server resolving
'91.250.13.204.relays.ordb.org' (in 'relays.ordb.org'?): 206.154.202.54#53
Oct 17 17:47:29 mxin2 named[750]: lame server resolving
'8.213.188.195.relays.ordb.org' (in 'relays.ordb.org'?): 206.154.202.54#53
Oct 17 17:47:29 mxin2 named[750]: lame server resolving
'94.134.141.64.relays.ordb.org' (in 'relays.ordb.org'?): 206.154.202.54#53
Oct 17 17:47:29 mxin2 named[750]: lame server resolving
'41.88.132.64.relays.ordb.org' (in 'relays.ordb.org'?): 205.139.192.54#53
Oct 17 17:47:29 mxin2 named[750]: lame server resolving
'91.249.13.204.relays.ordb.org' (in 'relays.ordb.org'?): 205.139.192.54#53
Oct 17 17:47:29 mxin2 named[750]: lame server resolving
'91.250.13.204.relays.ordb.org' (in 'relays.ordb.org'?): 205.139.192.54#53
Oct 17 17:47:29 mxin2 named[750]: lame server resolving
'147.91.61.64.relays.ordb.org' (in 'relays.ordb.org'?): 205.139.192.54#53
Oct 17 17:47:29 mxin2 named[750]: lame server resolving
'40.102.124.207.relays.ordb.org' (in 'relays.ordb.org'?): 205.139.192.54#53

Re-executing the same query manually through dig (at 205.139.192.54 or
206.154.202.54 directly) result in the proper answer being returned.

Downgrading to BIND 9.3.2-P1 causes these messages to go away.

Could this be a bug with BIND? Is BIND being more sensitive to lame
delegations in more recent versions? Best as we can tell, ordb.org is not
having any problems problems with the zone.

Any thoughts or help is very much appreciated.

Tom Daly

--
Thomas J. Daly
tom@dyndns.com
Dynamic Network Services, Inc.
http://www.dyndns.com/