slave: WARNING: recursion requested but not available
kcd at chrysler.com
Fri Jun 6 18:20:16 UTC 2014
On 6/6/2014 7:35 AM, Reindl Harald wrote:
> Am 06.06.2014 13:28, schrieb Matus UHLAR - fantomas:
>> On 06.06.14 13:13, Reindl Harald wrote:
>>> why does in case of asking the slave always come a
>>> "WARNING: recursion requested but not available"
>>> even if you dig a A-record he is authoritative?
>> because you request recursion and the server does not provide it.
>> use "dig +norecurse" not to request recursion
> i am asking a auth name server for it's own domain
> where and why do i request recursion in that case?
dig can't read your mind and thus know what you want to emulate. For
most queries issued via dig, either a) the user wants to emulate a stub
resolver, or b) the RD flag doesn't matter either way. That's why RD=1
is the default. The +norecurse flag -- setting RD=0 -- is one of the
ways you tell dig to emulate an iterative resolver when it composes its
query. An even better emulation includes setting a reasonable buffer
size via EDNS0, since most modern iterative resolvers do that too.
More information about the bind-users