Tuesday, January 19, 2010

main Google search page www.google.com on IPv6 too [UPDATE: Selected ISPs only]

UPDATE: Google is indeed on IPv6, but only via ISPs participating in "Google over IPv6". The post below was on a KPN Hotspot, which is connected to Xs4all, which is such a participator.
Pity. Normal users with non-IPv6 ISPs have to wait. :-(


Wow, even the mainstream Google page is on IPv6, too! So not only ipv6.google.com, but also www.google.com and www.google.nl

See below

sander@quirinius:~$ ping6 -c4 www.google.nl
PING www.google.nl(2a00:1450:8001::6a) 56 data bytes
64 bytes from 2a00:1450:8001::6a: icmp_seq=1 ttl=53 time=163 ms
64 bytes from 2a00:1450:8001::6a: icmp_seq=2 ttl=53 time=76.0 ms
64 bytes from 2a00:1450:8001::6a: icmp_seq=3 ttl=53 time=74.3 ms
64 bytes from 2a00:1450:8001::6a: icmp_seq=4 ttl=53 time=79.2 ms

--- www.google.nl ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 74.303/98.374/163.924/37.887 ms
sander@quirinius:~$

4 comments:

Anonymous said...

That depends if the DNS server that you are using is whitelisted by Google.
http://www.google.com/intl/en/ipv6/

chiel@tp:~$ host -t aaaa www.google.com
www.google.com CNAME www.l.google.com
www.l.google.com AAAA record currently not present

Ramon said...

Funny.. i'm using Google DNS and that doesn't return AAAA record for www.google.com

Jan said...

Google only whitelists nameservers for major IPv6 access providers, and only if they promise to maintain a stable IPv6 network.

They do this to avoid losing visitors because of problems in IPv6 routing...

Since google doesn't provide IPv6 access, it doesn't whitelist its own DNS servers.

Quirinius said...

Thanks for your reactions; indeed I was wrong or just too hopeful; I was using a KPN Hotspot on a Xs4all connection. As Xs4all is participating in Google's IPv6, I got IPv6 addresses and connections for mail.google.com and www.google.com.

On 'normal' connections, you only get IPv4 connections. :-(