Comments on: How to access Gmail and Google Reader over IPv6

By: Jeremy

Jeremy — Mon, 01 Mar 2010 00:27:14 +0000

Yes, I completely agree, and that is my approach now. (I use 2001:44b8:1::6 and 2001:44b8:2::6 as my resolvers.) But you’ll notice this post was written before such resolvers were available to the public.

By: Joshua Rogers

Joshua Rogers — Sat, 27 Feb 2010 16:23:55 +0000

Or just get whitelisted and use googles DNS servers.

Or if you use http://www.tunnelbroker.net, then just use he.net’s DNS resolvers (which are google whitelisted)

Google doesn’t want to hand out AAAA records to folks using IPv4 only.

By: TJ

TJ — Mon, 08 Dec 2008 22:34:32 +0000

WRT “I wonder what the likelihood of Google adding AAAA records to the main http://www.google.com domain is.” … the odds are very good if you are a member of their “trusted tester program” …

/TJ

By: Jari K

Jari K — Wed, 03 Dec 2008 18:24:05 +0000

Hi,

here’s what I defined in /etc/hosts to access Google maps over v6 (all on one line, of course):

2001:4860:0:1001::68 maps.google.com mt.google.com mt0.google.com mt1.google.com mt2.google.com mt3.google.com cbk0.google.com cbk1.google.com cbk2.google.com cbk3.google.com mw1.google.com mw2.google.com khm.google.com khm0.google.com khm1.google.com khm2.google.com khm3.google.com

As you can see, the address is 2001:4860:0:1001::68 for me.

- Jari

By: Jeremy

Jeremy — Fri, 28 Nov 2008 00:09:51 +0000

Thanks for the info. Interestingly, ipv6.google.com still resolves to what I wrote in the blog post for me. Perhaps it’s a regional thing.

Also, your test pages don’t seem to work. (The DNS doesn’t seem to work.) Other IPv6 sites definitely work for me, still.