One more note on this topic for our mutual education: We had an IP block acquired from Cogent where we submitted geolocation updates, but things kept reverting back to "Albany, NY"
That's because Cogent had a geofeed specifying Albany, NY for the whole /19. We were advised to make our own geofeed and publish it as smaller blocks because not unlike IP routing the longer subnet mask wins in most cases. So empirically this RFC method does work with at least some of the geolocation providers. -Adam From: [email protected] <[email protected]> Sent: Tuesday, October 31, 2023 3:15 PM To: 'AnimalFarm Microwave Users Group' <[email protected]> Subject: RE: Geolocation updates I guess the long term answer to this is going to be RFC8805 and RFC9092. You stick a CSV file on the web matching your IP blocks to a city and state, then add a comment on your IP Blocks with ARIN which contains a URL to the geofeed CSV. The geolocation providers who support this will periodically check ARIN WHOIS for those URL's and then once they have it they'll refresh multiple times per day. If they have other data they think is more accurate they can use that, but it lets you prime them with at least the right city and state. -Adam From: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]> > Sent: Sunday, October 22, 2023 2:03 PM To: 'AnimalFarm Microwave Users Group' <[email protected] <mailto:[email protected]> > Subject: Geolocation updates Which services do you need to update when you move IP blocks or get new blocks? I can't believe they all have their own separate databases. There must be smaller ones that key off of larger ones.
-- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
