Glue records and unable to resolve

[Kevin Darcy]

lamerfreak wrote:

>>>>Just about all nameservers shouldn't trust the glue for fenwaygroup.net,
>>>>as the nameservers are all under COM.  Named then queries for the
>>>>AAAA records for the nameservers and gets told by the servers for
>>>>mastermindpro.com that they don't exist.  Game over.
>>>>        
>>>>
>>>Question on this, if I may?
>>>
>>>What is the configuration directive in BIND9 (9.3.0, specifically) to
>>>enable/disable this behaviour?  I'm finding that mind looks up
>>>fenwaygroup.net successfully, and I'd rather have it in line.
>>>
>>>      
>>>
>>So you're looking for some sort of "please_poison_my_cache" option?
>>
>>- Kevin
>>    
>>
>
>Kinda.  I read and re-read the BIND9 administrator manual, tested,
>modified, and tweaked my configuration in some ways, and ... was just
>wondering how it's set up to not respond at all.  My server looks it
>up; my ISP's don't.  I'm more curious.
>
Glue-chasing and in-bailiwick-versus-out-of-bailiwick determination are 
things that have varied significantly between DNS implementations and 
even between versions of the same DNS implementation (e.g. BIND). I'm 
not aware of any way within any BIND version to configure the behavior, 
though, and I think the latest versions of BIND take the "safest" 
approach because of the cache-poisoning dangers of doing otherwise.

-Kevin