IPv6 products, community and services
Google over IPv6 "gotcha"
One of my colleague made me aware of this one today. I've seen this page in the past [http://www.google.com/intl/en/ipv6/] from Google and their IPv6 and didn't really read allt he details until today.
"Normally, if a DNS resolver requests an IPv6 address for a Google web site,
it will not receive one…
…but a DNS resolver with Google over IPv6 will receive an IPv6 address,
and its users will be able to connect to Google web sites using IPv6."
It looks like Google won't answer with its AAAA records to a DNS server if it has not been added to a white list ("qualified to Google Ipv6").
My explication: Google do not want their users to reach their web applications via a lame IPv6 connection when there's a fast and reliable IPv4 connection available. Modern operating systems prefer IPv6 and a dual stack user with a good IPv4 network and a lame IPv6 network will use the Ipv6 one to reach Google by default. If this is right I can say that they certainly care a lot for the user experience.... and the ability to display ads :)
What do you think of this?
P.S I don't think this applies to ipv6.google.com
"Normally, if a DNS resolver requests an IPv6 address for a Google web site,
it will not receive one…
…but a DNS resolver with Google over IPv6 will receive an IPv6 address,
and its users will be able to connect to Google web sites using IPv6."
It looks like Google won't answer with its AAAA records to a DNS server if it has not been added to a white list ("qualified to Google Ipv6").
My explication: Google do not want their users to reach their web applications via a lame IPv6 connection when there's a fast and reliable IPv4 connection available. Modern operating systems prefer IPv6 and a dual stack user with a good IPv4 network and a lame IPv6 network will use the Ipv6 one to reach Google by default. If this is right I can say that they certainly care a lot for the user experience.... and the ability to display ads :)
What do you think of this?
P.S I don't think this applies to ipv6.google.com
Comment
-
Comment by Tun Tun on July 20, 2010 at 10:45am -
We have native dual-stack as well as v6 peering with our internal upstream AS that has direct peering with Google which means we are only one AS-Hop away to Google AS15169. Our v6 ping and traceroute RTT shows less than 40ms to them.
I have a lab network with full dual-stack including DNS resolver. I was trying to have some user experience for our v6 folks to surf google's content over v6 transport. Understanding their policy, I dropped email to google-ipv6@google.com a month ago asking them how to get certified but no reply until now. I've also copied the same email and sent to their v6 evangelist, Lorenzo two weeks later. So far, I still haven't got any reply.
This makes me wonder if they actually have any clear policy and process to support v6 yet.
-
Comment by John R Baskind on February 3, 2010 at 7:56pm -
ipv6.google.com works fine
-
Comment by Mikael Lind on February 2, 2010 at 10:38am -
Google says it is because they can't meet the SLA requirements if they enable IPv6 for all users. They will loose less than 0.1% of the users who have something broken in their network which will make their connection fail and that is not acceptable to them. There will also be a timeout for a few users and that is apparently not acceptable for some of the SLAs.
-
Comment by Jan Herrygers on February 1, 2010 at 8:02pm -
I read that a while ago.
This is why I use the gogo6 nameservers.
But I think google just wants someone they can blame when things go wrong.
Note that only larger ISPs can join the v6 program, and they have to promise to troubleshoot/solve any connection problems for you.
Typically google: everything is beta.
Sponsors
IPv6 Resource Center
IPv6 Product Information
© 2013 Created by gogo6.
You need to be a member of gogoNET to add comments!
Join gogoNET