[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
L3: Google from DC via the Netherlands?
- Subject: L3: Google from DC via the Netherlands?
- From: stuart at tech.org (Stephen Stuart)
- Date: Sat, 07 Feb 2009 00:51:31 +0000
- In-reply-to: Your message of "Sat, 07 Feb 2009 01:43:02 +0100." <[email protected]>
> On Fri, Feb 06, 2009 at 12:05:41PM -0500, Peter Beckman wrote:
> > I'm OK to that IP as well, but when I query www.google.com, I get multiple
> > IPs, but here are the ones that in in 147:
> >
> > DNS Server IP Route (for me)
> > 205.234.170.217 (tiggee) 74.125.79.147 Amsterdam
> > 208.67.222.222 (opendns) 64.233.183.147 Amsterdam
> > 4.2.2.1 (verizon) 74.125.19.147 San Jose
> > 198.6.1.3 (uu.net/verizon) 74.125.47.147 Washington DC (yay)
> >
> > That's a lot of different answers for the same question!
>
> And you can add this one to your list:
>
> DNS Server IP
> 212.27.40.240 (free/proxad) 2001:4860:A003:0:0:0:0:68
>
> $ host -t AAAA www.google.com 212.27.40.240
> www.google.com CNAME www.l.google.com
> www.l.google.com AAAA 2001:4860:A003:0:0:0:0:68
>
> As you can see, no need for http://ipv6.google.com/ to reach Google
> over IPv6 using default DNS resolver provided by some French ISPs.
> www.google.com starts to be resolved as an IPv4/IPv6 website.
Certain IPv6-capable networks are able to get AAAA responses from us,
yes. Read:
http://www.google.com/ipv6/
Stephen