nanog mailing list archives
Re: DNS resolver reaction to non-reachable authoritative DNS server
From: Doug Barton <dougb () dougbarton us>
Date: Thu, 13 Mar 2014 18:29:28 -0700
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
Current thread:
- DNS resolver reaction to non-reachable authoritative DNS server Anurag Bhatia (Mar 13)
- Re: DNS resolver reaction to non-reachable authoritative DNS server Doug Barton (Mar 13)
- Re: DNS resolver reaction to non-reachable authoritative DNS server Mark Andrews (Mar 13)
- Re: DNS resolver reaction to non-reachable authoritative DNS server Doug Barton (Mar 13)
- Re: DNS resolver reaction to non-reachable authoritative DNS server Anurag Bhatia (Mar 14)
- Re: DNS resolver reaction to non-reachable authoritative DNS server Mark Andrews (Mar 13)
- Re: DNS resolver reaction to non-reachable authoritative DNS server Doug Barton (Mar 13)