Re: NOTZONE response

[Brian W. <bwe...@xb...>]

> On Jun 22, 2016, at 7:02 AM, Alastair Donlon <ala...@op...> wrote:
> 
> 
> It looks like the Lookup class returns a status of Lookup.TRY_AGAIN when 
> the server responds with a NOTZONE status. I find that a little bit 
> surprising - I would have expected this response to be seen as some kind 
> of fatal error. Is there something I'm misunderstanding either about 
> NOTZONE or the Lookup class?

I believe that it’s treating any unexpected rcode as something which could be a transient problem, and definitely shouldn’t cause the Lookup to immediately fail (as the UNRECOVERABLE errors do).  Simply treating an unexpected rcode as an unrecoverable error isn’t enough, because a single Lookup will often send multiple queries to each of multiple servers, and getting something like NOTZONE for one of those queries doesn’t necessarily mean total failure at all.  It’s possible that there could be some additional code handling the case when all queries get unexpected rcode values, but that’s a pretty special case.

Brian