L3: Google from DC via the Netherlands?
stuart at tech.org
Fri Feb 6 18:51:31 CST 2009
> 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)
> > 126.96.36.199 (tiggee) 188.8.131.52 Amsterdam
> > 184.108.40.206 (opendns) 220.127.116.11 Amsterdam
> > 18.104.22.168 (verizon) 22.214.171.124 San Jose
> > 126.96.36.199 (uu.net/verizon) 188.8.131.52 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
> 184.108.40.206 (free/proxad) 2001:4860:A003:0:0:0:0:68
> $ host -t AAAA www.google.com 220.127.116.11
> 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,
More information about the NANOG