[162394] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Google incorrect IPv6 GeoIP

daemon@ATHENA.MIT.EDU (Scott Howard)
Fri Apr 12 21:48:35 2013

In-Reply-To: <CAL9jLabvpg=91DxGYqQMf95BGEYinDF8-YywPTgMxU3MFcBO=A@mail.gmail.com>
Date: Fri, 12 Apr 2013 18:48:23 -0700
From: Scott Howard <scott@doc.net.au>
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

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

home help back first fref pref prev next nref lref last post