[169752] in North American Network Operators' Group
Re: DNS resolver reaction to non-reachable authoritative DNS server
daemon@ATHENA.MIT.EDU (Doug Barton)
Thu Mar 13 21:30:35 2014
Date: Thu, 13 Mar 2014 18:29:28 -0700
From: Doug Barton <dougb@dougbarton.us>
CC: nanog@nanog.org
In-Reply-To: <20140314002315.B75C31162426@rock.dv.isc.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 3/13/2014 5:23 PM, Mark Andrews wrote:
>> If your customers are using BIND there is a flag you can supply to named
>> >to cause it to operate only in IPv4. That would avoid this problem
>> >altogether.
>
> And is basically not needed as the IP stack (with the exception of
> Solaris) informs named when there isn't a route to the destination
> and named moves onto the next address to try.
Sure, but by using the flag you skip that step, and the accompanying
error message in the logs.
The fact that this issue has risen to the level of "annoyance" rather
than just "oddity" as it used to be is actually a good thing. It's a
sign that more and more sites are deploying IPv6 for critical
infrastructure.
Doug
