[114124] in North American Network Operators' Group
Re: how to fix incorrect GeoIP data?
daemon@ATHENA.MIT.EDU (William F. Maton Sotomayor)
Fri May 1 16:44:58 2009
Date: Fri, 1 May 2009 16:43:59 -0400 (EDT)
From: "William F. Maton Sotomayor" <wmaton@ryouko.imsb.nrc.ca>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <75cb24520905011329t6bb7f6fak64a1cc93b90f0b3c@mail.gmail.com>
Cc: nanog@nanog.org
Reply-To: wmaton@ryouko.imsb.nrc.ca
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Fri, 1 May 2009, Christopher Morrow wrote:
> On Fri, May 1, 2009 at 2:06 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> On Fri, 1 May 2009, Frank Bulk wrote:
>>
>>> What we need is a "master update" form where Akamai, Google, Maxmind,
>>> hostip.info, Geobytes, ip2location, ipgeo, etc can be notified about
>>> changes.
>>
>> Perhaps we as the ISP community need to realise that we need to somehow
>> publish this data (town or something alike) via some kind of standardized
>> API?
>
> hey lookie! dns TXT records!! :)
LOC records too. :-)
dig @prisoner.iana.org hostname.as112.net any
;; QUESTION SECTION:
;hostname.as112.net. IN ANY
;; ANSWER SECTION:
hostname.as112.net. 604800 IN SOA as112.gigafed.net.
dns.ryouko.imsb.nrc.ca. 1 604800 60 604800 604800
hostname.as112.net. 604800 IN LOC 45 25 0.000 N 75 42 0.000
W 80.00m 1m 10000m 10m
Helpful for folks like CAIDA too.
wfms