Have we been opted out of IPv6 AAAA resolution?
p.mayers at imperial.ac.uk
Wed Jun 6 18:50:08 CEST 2012
On 06/06/12 17:39, Shumon Huque wrote:
> Thanks! I'm glad Google is being transparent about the contents
> of the blacklist. It would be even more helpful to proactively
> provide diagnostic details of the "brokenness" they are measuring
> to those that are blacklisted, instead of waiting for folks to
> contact them. Silently blacklisting resolvers isn't helping the
> cause of IPv6 adoption very well.
True, although in fairness to Google, the data protection implications
of passing useful data (source IP, port, timestamp) back to owner sites
> Thanks. Please share what you find out! I'm sure many others are
> I'd be interested in knowing who besides Google is performing selective
> delivery of AAAA records. And if specific details are published
I've had confirmation from other sites that a) they have nameservers in
that list, and b) those nameservers also can't see AAAA records for
www.facebook.com. Whether Google/Facebook are sharing the list or using
similar "broken detection" metrics I don't know.
I'm also pretty sure that Yahoo are performing AAAA filtering:
[root at rdns1 ~]# dig -b 22.214.171.124 +short @yf1.yahoo.com.
[root at rdns1 ~]# dig -b 126.96.36.199 +short @yf1.yahoo.com.
[root at rdns1 ~]#
...and a colleague points out that Bing (via Akamai) are also filtering.
More information about the ipv6-ops