In message <[email protected]>, Brett Watson writes: > On Apr 19, 2010, at 11:02 AM, Edward Lewis wrote: > > > But the problem with IPv6 connectivity testing is that the granularity (ne > eded for tailoring) is not very consistent. > > While I somewhat entertained this whole idea at first, that's the conclusion > I came to. I think there are too many corner cases where determining whether > the client system making the original query has v6 connectivity or not is jus > t not possible. That's not the only issue with this idea but I think a signif > icant one.
And the solution is "just deploy IPv6 where ever you can". Having IPv6 deployed stops these boxes auto configuring IPv6 using methods that are blocked. Turn it on for your nameservers, authoritative and recursive. Turn it on for your clients nets. Selectively turn it on for other services. MTA are good candidates as they are normally not real time. Check that your load balancer actually gives good answers for AAAA queries as too many of them are mis-configured, correct rcode and correct SOA. Report ones that return bad answers. I've actually had two "Thank You"s in the last month doing that to ones that have shown up on bind-users just by Bcc the bind-users reply. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected] _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
