Factors, actions influencing the possibility/timing of IDR for IPv6-basedrouting domains?
nicolas.braudsantoni at gmail.com
Fri Jul 17 15:44:56 CEST 2009
2009/7/16 Anthony Roberts <ipv6-ops at arbitraryconstant.com>:
> Good point. I don't think all v6 hosts are getting Google's AAAAs yet, but
> I imagine that's going to improve with time as v6 networks become better
> connected with each other.
Google authoritative DNS won't give you the AAAA records unless they
recognize the IPv4 address of your DNS resolver as an IPv6 compliant
host (they just lookup a list of hosts that requested to get the AAAA
More information here : http://www.google.com/intl/en/ipv6/
> I've been following the BEHAVE NAT64 mailing list -- they've now got a
> draft to allow hosts to learn the NAT64 translation prefix and take
> appropriate action internally for situations like this where DNS
> translation can't occur. Google cache links aren't the only use case that
> may be impacted. That won't work for "legacy" v6 hosts that don't support
> this, but moving forward at least there's a better developed set of tools
> to mitigate these sorts of issues. "Foo is broken in v6" is much worse than
> "You need Windows N+1 SP2 to use foo in v6".
More information about the ipv6-ops