[169768] in North American Network Operators' Group
Re: DNS resolver reaction to non-reachable authoritative DNS server
daemon@ATHENA.MIT.EDU (Anurag Bhatia)
Fri Mar 14 16:00:00 2014
In-Reply-To: <53225B78.9010902@dougbarton.us>
From: Anurag Bhatia <me@anuragbhatia.com>
Date: Sat, 15 Mar 2014 01:28:45 +0530
To: Doug Barton <dougb@dougbarton.us>
Cc: NANOG Mailing List <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Got it!
Thankyou very much for help. Have a good weekend ahead.
On Fri, Mar 14, 2014 at 6:59 AM, Doug Barton <dougb@dougbarton.us> wrote:
> 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
>
>
>
--
Anurag Bhatia
anuragbhatia.com
Linkedin <http://in.linkedin.com/in/anuragbhatia21> |
Twitter<https://twitter.com/anurag_bhatia>
Skype: anuragbhatia.com
PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2
