Re: Google incorrect IPv6 GeoIP

[Yang Yu <yang.yu.list () gmail com>]

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