Already since April 2009 ;) The only requirement for "Google IPv6" is that one has IPv6 connectivity and that one uses a DNS resolver which is whitelisted, thus using our Recursive DNS Cache Service will do that just fine.

Actually an IPv6-transport-only DNS server doesn't necessarily fix the problem because a dual-stacked resolver may reach it and return the result to an IPv4-transport-only client (or more specifically a client with broken IPv6 connectivity). I get why they're doing it. From one point of view it's broken, but apparently there is enough of a problem with faulty resolvers causing IPv6 timeouts that they felt the need for this workaround.

An IPv6 only server would be out of luck i think. Google;s nameservers only have A records, and IPv4 glue. They did say on their faq that if enough tunnel users are interested in being able to query directly for the AAAA records, they might consider it. I wrote them a few hours ago, got an answer back, explaining why they restricting it and such. To be honest, as much as it wasnt what I was hoping for, they did write back, and really quickly no less. I wrote them back again, told them what my IPv4 address is, and all but outright begged to be allowed to query them directly for v6. What I don't understand is, their concern seems to be that if IPv6 is enabled, users with just IPv4 or with both will have problems on their site. arin.net is ipv6 enabled, so is ripe, apnic, etc. Root servers etc have IPv6, if it would so get in the way, or slow things down, why aren't those affected too?

I'm much in the same boat. The sign in the hallway says "Welcome to wsrcc.com population: 2". There is no way google will peer their dns with me, so I needed to hack it a bit. What I did was grab some IPv6 addresses for ipv6.google.com and shoved them into /etc/hosts with some likely-sounding hostnames that I wanted to overlay. This is what I have so far and gmail, buzz and search via www.google.com seem to go over IPv6 now. I'm no doubt missing some choice hostnames, but that is just a matter of running a long enough wireshark run to catch them all. Ok. I admit this is a bit evil, but what choices does google give us??? # add to /etc/hosts: # # get these ipv6 addresses via: host ipv6.google.com # 2001:4860:8010::93 ipv6.google.com www.google.com mail.google.com gmail.com 2001:4860:8010::63 ipv6.google.com www.google.com mail.google.com gmail.com 2001:4860:8010::67 ipv6.google.com www.google.com mail.google.com gmail.com 2001:4860:8010::68 ipv6.google.com www.google.com mail.google.com gmail.com #

it works over sixxs tunnel, goto ipv6.google.com!

root@Egal-11:~# ping6 ipv6.google.com PING ipv6.google.com(2a00:1450:8007::68) 56 data bytes 64 bytes from 2a00:1450:8007::68: icmp_seq=1 ttl=56 time=36.6 ms 64 bytes from 2a00:1450:8007::68: icmp_seq=2 ttl=56 time=36.7 ms 64 bytes from 2a00:1450:8007::68: icmp_seq=3 ttl=56 time=37.3 ms 64 bytes from 2a00:1450:8007::68: icmp_seq=4 ttl=56 time=37.0 ms 64 bytes from 2a00:1450:8007::68: icmp_seq=5 ttl=56 time=37.2 ms