[162395] in North American Network Operators' Group
Re: Google incorrect IPv6 GeoIP
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Fri Apr 12 22:04:45 2013
In-Reply-To: <CACnPsNWCTZi1_GXMeyKeQtfea-9a4Kq1y=nuutrNi55Vh91pjQ@mail.gmail.com>
Date: Fri, 12 Apr 2013 22:04:33 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Scott Howard <scott@doc.net.au>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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)
