[114128] in North American Network Operators' Group
Re: how to fix incorrect GeoIP data?
daemon@ATHENA.MIT.EDU (Mark Foster)
Fri May 1 17:58:14 2009
Date: Sat, 2 May 2009 09:58:08 +1200 (NZST)
From: Mark Foster <blakjak@blakjak.net>
To: Peter Beckman <beckman@angryox.com>
In-Reply-To: <alpine.BSF.2.00.0905011719120.3244@nog.angryox.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> I don't think self-reporting is the answer.
>
> You MIGHT be able to determine location based on a traceroute, though
> anycast would surely derail such attempts. I suspect most people rely on
> 3rd party GeoIP databases, and that those companies aren't interested in
> hearing from you about your location change, mostly because they are
> worried that if they do, the evildoers will overrun them with bad
> requests, or bait and switch, making their data less accurate than it is
> now without your block being correct.
>
Having recently leapt through a few GeoIP hoops to see about getting
records fixed[1], perhaps the NANOG wiki could feature 'known ways to
fix GeoIP' and be used as a reference?
Seems to be something that's going to be more, not less, significant to
customers and network operators alike going forward.
Mark.
[1] http://www.merit.edu/mail.archives/nanog/msg13895.html
