Re: Google incorrect IPv6 GeoIP

2013-04-15 Thread Yang Yu
Still getting redirected Resolving www.google.com... 2607:f8b0:400c:c04::69, 74.125.26.104, 74.125.26.99, ... Connecting to www.google.com|2607:f8b0:400c:c04::69|:443... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredire

Re: Google incorrect IPv6 GeoIP

2013-04-15 Thread Christopher Morrow
On Fri, Apr 12, 2013 at 11:37 PM, Yang Yu wrote: > DNS is actually working correctly I think. > 1) The outputs are from Dreamhost Ashburn, but I saw the same result > over IPv6 at Dreamhost LAX. Different DNS servers. > over ipv6 there might not be enough distinction between locations ... > 2)

Re: Google incorrect IPv6 GeoIP

2013-04-12 Thread Yang Yu
DNS is actually working correctly I think. 1) The outputs are from Dreamhost Ashburn, but I saw the same result over IPv6 at Dreamhost LAX. Different DNS servers. 2) ping and ping6 times are pretty much the same. I suppose they are served by the same Google cluster/CDN. 3) No redirect over IPv4

Re: Google incorrect IPv6 GeoIP

2013-04-12 Thread Christopher Morrow
On Fri, Apr 12, 2013 at 9:48 PM, Scott Howard wrote: > On Fri, Apr 12, 2013 at 5:58 PM, Christopher Morrow < > morrowc.li...@gmail.com> wrote: > >> no you don't... the dreamhost example used the google ARIN allocation >> 2607:: this example uses the 2404 APNIC allocation. >> >> note that thi

Re: Google incorrect IPv6 GeoIP

2013-04-12 Thread Scott Howard
On Fri, Apr 12, 2013 at 5:58 PM, Christopher Morrow wrote: > no you don't... the dreamhost example used the google ARIN allocation > 2607:: this example uses the 2404 APNIC allocation. > > note that this may still be 'wrong', but .. it's a different wrong. :) > But likely caused by exactly

Re: Google incorrect IPv6 GeoIP

2013-04-12 Thread Christopher Morrow
On Fri, Apr 12, 2013 at 11:06 AM, cb.list6 wrote: > Heather, > > I see the same thing from my arpnetworks vps > > no you don't... the dreamhost example used the google ARIN allocation 2607:: this example uses the 2404 APNIC allocation. note that this may still be 'wrong', but .. it's a diff

Re: Google incorrect IPv6 GeoIP

2013-04-12 Thread cb.list6
Heather, I see the same thing from my arpnetworks vps [cbyrne@chair6 ~]$ traceroute6 www.google.com traceroute6 to www.google.com (2404:6800:4003:801::1010) from 2607:f2f8:a8e0::2, 64 hops max, 12 byte packets 1 2607:f2f8:a8e0::1 1.657 ms 0.976 ms 0.750 ms 2 2001:504:13::

Re: Google incorrect IPv6 GeoIP

2013-04-12 Thread Heather Schiller
Forwarded to folks I think should be able to help.. --Heather On Thu, Apr 11, 2013 at 7:13 PM, Yang Yu wrote: > For some reason Google redirects requests from Dreamhost's IPv6 block > 2607:f298::/32 to google.com.hk > > $ wget http://www.google.com > --2013-04-11 16:06:45-- http://www.google

Google incorrect IPv6 GeoIP

2013-04-11 Thread Yang Yu
For some reason Google redirects requests from Dreamhost's IPv6 block 2607:f298::/32 to google.com.hk $ wget http://www.google.com --2013-04-11 16:06:45-- http://www.google.com/ Resolving www.google.com... 2607:f8b0:400c:c01::93, 173.194.75.99, 173.194.75.147, ... Connecting to www.google.com|260