bind 9.16.7 Odd query error (Borja Marcos)

[Mark Andrews]

No, it’s just fetches per query taking effect.  With a empty cache there are just too many queries made looking up addresses of name servers. You can raise the default slightly. 

-- 
Mark Andrews

> On 1 Oct 2020, at 01:29, Borja Marcos <borjam at sarenet.es> wrote:
> 
> 
> 
>> On 30 Sep 2020, at 15:29, Bob McDonald <bmcdonaldjr at gmail.com> wrote:
>> 
>> Same thing here. Here's what I found.
>> 
>> 1) there's and old version of the root hints file. Nov 2017. Current is sept 2020. New one didn't change things. I'll look at my other setup which slaves the root.
>>   Caveat: I'm running FreeBSD 12.1
>> 2) Upon executing the dig a second time, it resolves.
>> 
>> Almost looks like some sort of priming issue.
> 
> Phew, not alone. I thought something similar, I see the same problem either “secondarying" the root zone
> or using a root.hints file.
> 
> Curiously it works perfectly when I disable IPv6. I can get a packet trace but with all the DNSSEC stuff it
> gets crazy to check.
> 
> I was wondering, what kind of errors can fall into that “default/unspecified” error cathegory?
> 
> A race condition in the cache?
> 
> 
> 
> 
> 
> Borja.
> 
> 
> 
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
> 
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users