www.google.com has aaaa 2a00:1450:4008:c00::69
www.youtube.com has aaaa 2a00:1450:4008:c00::be
www.facebook.com has aaaa 2620::1c00:0:face:b00c:0:1
www.bcc.com has aaaa 2001:4b10:bbc::1
Resolving AAAA records doesn't have much to do with IPv6 connectivity. The whole point today is to see what happens when clients receive AAAA records in addition to A records. If a misconfigured client thinks it can use IPv6 but can't, then the existence of that AAAA causes problems.
That's true.
But i think it's real good that these big sites add aaaa records for today. Hopefully the results will show that the percentage of broken users is really small.
Someone has to start deploying ipv6 - either isps or content providers.
www.google.com has aaaa 2a00:1450:4008:c00::69 www.youtube.com has aaaa 2a00:1450:4008:c00::be www.facebook.com has aaaa 2620::1c00:0:face:b00c:0:1 www.bcc.com has aaaa 2001:4b10:bbc::1
checked with ipv6 check @ http://www.upordown.de/www.youtube.com