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|2607:f8b0:400c:c01::93|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1365721636015681&usg=AFQjCNEa0yI6UdIVf1tqLtCw3qrBC6Akww [following] --2013-04-11 16:06:46-- http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1365721636015681&usg=AFQjCNEa0yI6UdIVf1tqLtCw3qrBC6Akww Resolving www.google.com.hk... 2607:f8b0:400c:c01::6a, 173.194.75.105, 173.194.75.99, ... Connecting to www.google.com.hk|2607:f8b0:400c:c01::6a|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.google.com.hk/ [following] --2013-04-11 16:06:46-- http://www.google.com.hk/ Reusing existing connection to www.google.com.hk:80. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: “index.html” The report IP problem form (https://support.google.com/websearch/contact/ip?rd=1) does not think IPv6 addresses are valid. Can someone help with this issue? Thanks. Yang
Forwarded to folks I think should be able to help.. --Heather On Thu, Apr 11, 2013 at 7:13 PM, Yang Yu <yang.yu.list@gmail.com> 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.com/ Resolving www.google.com... 2607:f8b0:400c:c01::93, 173.194.75.99, 173.194.75.147, ... Connecting to www.google.com|2607:f8b0:400c:c01::93|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1365721636015681&usg=AFQjCNEa0yI6UdIVf1tqLtCw3qrBC6Akww [following] --2013-04-11 16:06:46--
http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1365721636015681&usg=AFQjCNEa0yI6UdIVf1tqLtCw3qrBC6Akww Resolving www.google.com.hk... 2607:f8b0:400c:c01::6a, 173.194.75.105, 173.194.75.99, ... Connecting to www.google.com.hk|2607:f8b0:400c:c01::6a|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.google.com.hk/ [following] --2013-04-11 16:06:46-- http://www.google.com.hk/ Reusing existing connection to www.google.com.hk:80. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: “index.html”
The report IP problem form (https://support.google.com/websearch/contact/ip?rd=1) does not think IPv6 addresses are valid.
Can someone help with this issue?
Thanks.
Yang
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::1a 1.728 ms 10.591 ms 0.756 ms 3 2001:4860:1:1:0:1b1b:0:19 0.873 ms 0.907 ms 0.833 ms 4 2001:4860::1:0:29b3 1.195 ms 138.964 ms 2001:4860::1:0:991 1.633 ms 5 2001:4860::8:0:2996 1.645 ms 2001:4860::8:0:2995 1.929 ms 1.484 ms 6 2001:4860::1:0:47 99.059 ms 99.272 ms 2001:4860::1:0:75 99.079 ms 7 2001:4860::1:0:298 99.372 ms 111.549 ms 99.972 ms 8 2001:4860::1:0:26ff 103.146 ms 103.317 ms 103.029 ms 9 2001:4860::1:0:337f 166.821 ms 203.479 ms 166.468 ms 10 2001:4860:0:1::18f 167.021 ms 167.378 ms 166.896 ms 11 2404:6800:8000:4::e 167.039 ms 167.099 ms 167.254 ms [cbyrne@chair6 ~]$ dig www.google.com aaaa ; <<>> DiG 9.6.-ESV-R3 <<>> www.google.com aaaa ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50127 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;www.google.com. IN AAAA ;; ANSWER SECTION: www.google.com. 15 IN AAAA 2404:6800:4003:801::1010 ;; AUTHORITY SECTION: google.com. 271198 IN NS ns1.google.com. google.com. 271198 IN NS ns3.google.com. google.com. 271198 IN NS ns2.google.com. google.com. 271198 IN NS ns4.google.com. ;; ADDITIONAL SECTION: ns1.google.com. 61968 IN A 216.239.32.10 ns3.google.com. 61968 IN A 216.239.36.10 ns4.google.com. 61968 IN A 216.239.38.10 ns2.google.com. 61968 IN A 216.239.34.10 ;; Query time: 1 msec ;; SERVER: 208.79.88.7#53(208.79.88.7) ;; WHEN: Fri Apr 12 08:04:59 2013 ;; MSG SIZE rcvd: 196 [cbyrne@chair6 ~]$ On Fri, Apr 12, 2013 at 7:53 AM, Heather Schiller <hschiller@google.com> wrote:
Forwarded to folks I think should be able to help..
--Heather
On Thu, Apr 11, 2013 at 7:13 PM, Yang Yu <yang.yu.list@gmail.com> 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.com/ Resolving www.google.com... 2607:f8b0:400c:c01::93, 173.194.75.99, 173.194.75.147, ... Connecting to www.google.com|2607:f8b0:400c:c01::93|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1365721636015681&usg=AFQjCNEa0yI6UdIVf1tqLtCw3qrBC6Akww [following] --2013-04-11 16:06:46--
http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1365721636015681&usg=AFQjCNEa0yI6UdIVf1tqLtCw3qrBC6Akww Resolving www.google.com.hk... 2607:f8b0:400c:c01::6a, 173.194.75.105, 173.194.75.99, ... Connecting to www.google.com.hk|2607:f8b0:400c:c01::6a|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.google.com.hk/ [following] --2013-04-11 16:06:46-- http://www.google.com.hk/ Reusing existing connection to www.google.com.hk:80. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: “index.html”
The report IP problem form (https://support.google.com/websearch/contact/ip?rd=1) does not think IPv6 addresses are valid.
Can someone help with this issue?
Thanks.
Yang
On Fri, Apr 12, 2013 at 11:06 AM, cb.list6 <cb.list6@gmail.com> 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 different wrong. :)
[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::1a 1.728 ms 10.591 ms 0.756 ms 3 2001:4860:1:1:0:1b1b:0:19 0.873 ms 0.907 ms 0.833 ms 4 2001:4860::1:0:29b3 1.195 ms 138.964 ms 2001:4860::1:0:991 1.633 ms 5 2001:4860::8:0:2996 1.645 ms 2001:4860::8:0:2995 1.929 ms 1.484 ms 6 2001:4860::1:0:47 99.059 ms 99.272 ms 2001:4860::1:0:75 99.079 ms 7 2001:4860::1:0:298 99.372 ms 111.549 ms 99.972 ms 8 2001:4860::1:0:26ff 103.146 ms 103.317 ms 103.029 ms 9 2001:4860::1:0:337f 166.821 ms 203.479 ms 166.468 ms 10 2001:4860:0:1::18f 167.021 ms 167.378 ms 166.896 ms 11 2404:6800:8000:4::e 167.039 ms 167.099 ms 167.254 ms [cbyrne@chair6 ~]$ dig www.google.com aaaa
; <<>> DiG 9.6.-ESV-R3 <<>> www.google.com aaaa ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50127 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
;; QUESTION SECTION: ;www.google.com. IN AAAA
;; ANSWER SECTION: www.google.com. 15 IN AAAA 2404:6800:4003:801::1010
;; AUTHORITY SECTION: google.com. 271198 IN NS ns1.google.com. google.com. 271198 IN NS ns3.google.com. google.com. 271198 IN NS ns2.google.com. google.com. 271198 IN NS ns4.google.com.
;; ADDITIONAL SECTION: ns1.google.com. 61968 IN A 216.239.32.10 ns3.google.com. 61968 IN A 216.239.36.10 ns4.google.com. 61968 IN A 216.239.38.10 ns2.google.com. 61968 IN A 216.239.34.10
;; Query time: 1 msec ;; SERVER: 208.79.88.7#53(208.79.88.7) ;; WHEN: Fri Apr 12 08:04:59 2013 ;; MSG SIZE rcvd: 196
[cbyrne@chair6 ~]$
On Fri, Apr 12, 2013 at 7:53 AM, Heather Schiller <hschiller@google.com> wrote:
Forwarded to folks I think should be able to help..
--Heather
On Thu, Apr 11, 2013 at 7:13 PM, Yang Yu <yang.yu.list@gmail.com> 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.com/ Resolving www.google.com... 2607:f8b0:400c:c01::93, 173.194.75.99, 173.194.75.147, ... Connecting to www.google.com|2607:f8b0:400c:c01::93|:80... connected. HTTP request sent, awaiting response... 302 Found Location:
[following] --2013-04-11 16:06:46--
Resolving www.google.com.hk... 2607:f8b0:400c:c01::6a, 173.194.75.105, 173.194.75.99, ... Connecting to www.google.com.hk|2607:f8b0:400c:c01::6a|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.google.com.hk/ [following] --2013-04-11 16:06:46-- http://www.google.com.hk/ Reusing existing connection to www.google.com.hk:80. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: “index.html”
The report IP problem form (https://support.google.com/websearch/contact/ip?rd=1) does not think IPv6 addresses are valid.
Can someone help with this issue?
Thanks.
Yang
On Fri, Apr 12, 2013 at 5:58 PM, Christopher Morrow <morrowc.lists@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 this may still be 'wrong', but .. it's a different wrong. :)
But likely caused by exactly the same problem - with the distinction between between GeoIP of the DNS server and GeoIP of the client itself. (Keeping in mind that the DNS lookup could be occurring over IPv4, especially in the first example) Scott
On Fri, Apr 12, 2013 at 9:48 PM, Scott Howard <scott@doc.net.au> wrote:
On Fri, Apr 12, 2013 at 5:58 PM, Christopher Morrow < morrowc.lists@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 this may still be 'wrong', but .. it's a different wrong. :)
But likely caused by exactly the same problem - with the distinction between between GeoIP of the DNS server and GeoIP of the client itself.
(Keeping in mind that the DNS lookup could be occurring over IPv4, especially in the first example)
except that the dreamhost example actually looked correct to me? (dreamhost is in phx / lax or something similar... so a US answer seems on the ball)
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 $dig www.google.com AAAA ; <<>> DiG 9.7.3 <<>> www.google.com AAAA ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30269 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.google.com. IN AAAA ;; ANSWER SECTION: www.google.com. 209 IN AAAA 2607:f8b0:400c:c04::63 ;; Query time: 0 msec ;; SERVER: 208.113.157.201#53(208.113.157.201) ;; WHEN: Fri Apr 12 20:25:24 2013 ;; MSG SIZE rcvd: 60 $ traceroute 2607:f8b0:400c:c04::63 traceroute to 2607:f8b0:400c:c04::63 (2607:f8b0:400c:c04::63), 30 hops max, 80 byte packets 4 2607:f298:5:0:208:113:156:1 (2607:f298:5:0:208:113:156:1) 0.175 ms 0.179 ms 0.156 ms 5 2001:438:fffe::5c5 (2001:438:fffe::5c5) 0.197 ms 0.186 ms 0.183 ms 6 2001:438:ffff::407d:1882 (2001:438:ffff::407d:1882) 0.233 ms 0.231 ms 0.361 ms 7 2001:438:ffff::407d:c52 (2001:438:ffff::407d:c52) 0.309 ms 0.288 ms 0.288 ms 8 2001:4860::1:0:9ff (2001:4860::1:0:9ff) 1.529 ms 1.533 ms 1.601 ms 9 2001:4860::8:0:3cda (2001:4860::8:0:3cda) 2.177 ms 0.968 ms 2001:4860::8:0:3cd9 (2001:4860::8:0:3cd9) 1.381 ms 10 2001:4860::8:0:33b2 (2001:4860::8:0:33b2) 12.431 ms 2001:4860::8:0:33b3 (2001:4860::8:0:33b3) 44.297 ms 2001:4860::8:0:33b2 (2001:4860::8:0:33b2) 12.371 ms 11 2001:4860::2:0:33b1 (2001:4860::2:0:33b1) 12.406 ms 2001:4860::2:0:33b0 (2001:4860::2:0:33b0) 13.059 ms 2001:4860::2:0:33b1 (2001:4860::2:0:33b1) 12.343 ms 12 vh-in-x63.1e100.net (2607:f8b0:400c:c04::63) 12.872 ms 12.845 ms 12.899 ms $ dig www.google.com ; <<>> DiG 9.7.3 <<>> www.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63365 ;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.google.com. IN A ;; ANSWER SECTION: www.google.com. 244 IN A 74.125.26.99 www.google.com. 244 IN A 74.125.26.105 www.google.com. 244 IN A 74.125.26.104 www.google.com. 244 IN A 74.125.26.147 www.google.com. 244 IN A 74.125.26.106 www.google.com. 244 IN A 74.125.26.103 ;; Query time: 0 msec ;; SERVER: 208.113.157.201#53(208.113.157.201) ;; WHEN: Fri Apr 12 20:24:49 2013 ;; MSG SIZE rcvd: 128 wget -4 http://www.google.com --2013-04-12 20:29:26-- http://www.google.com/ Resolving www.google.com... 74.125.26.103, 74.125.26.99, 74.125.26.104, ... Connecting to www.google.com|74.125.26.103|:80... connected. HTTP request sent, awaiting response... 200 OK Yang On Fri, Apr 12, 2013 at 9:48 PM, Scott Howard <scott@doc.net.au> wrote:
On Fri, Apr 12, 2013 at 5:58 PM, Christopher Morrow <morrowc.lists@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 this may still be 'wrong', but .. it's a different wrong. :)
But likely caused by exactly the same problem - with the distinction between between GeoIP of the DNS server and GeoIP of the client itself.
(Keeping in mind that the DNS lookup could be occurring over IPv4, especially in the first example)
Scott
On Fri, Apr 12, 2013 at 11:37 PM, Yang Yu <yang.yu.list@gmail.com> 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) 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
ok, so today I'm not seeing a redirect happening... want to try again? maybe things got worked out? or my testing tool is busted :)
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=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1366057169806151&usg=AFQjCNEQcW1Bg7ROZRYzpFJC-f99YXGF8Q [following] --2013-04-15 13:18:59-- http://www.google.com.hk/url?sa=p&hl=zh-CN&pref=hkredirect&pval=yes&q=http://www.google.com.hk/&ust=1366057169806151&usg=AFQjCNEQcW1Bg7ROZRYzpFJC-f99YXGF8Q Resolving www.google.com.hk... 2607:f8b0:400c:c04::69, 74.125.26.103, 74.125.26.106, ...
participants (5)
-
cb.list6 -
Christopher Morrow -
Heather Schiller -
Scott Howard -
Yang Yu