Hi,
What’s the proper way to specify the location of prefixes within a larger prefix? For example, we purchased a /17 and it is registered in ARIN as being located in our home town. However, smaller prefixes within that /17 are located in different areas of VA and NC, and people are complaining about location services showing them in the wrong area. Not sure how to “properly” fix it.
Thanks,
Ben
* Create assignment objects in ARIN for your longer-prefixes based on customer and/or region with appropriate geographic info,
* Make sure your forward and reverse DNS are accurate -- I'm told some geo-location databases look at this if you put geographic info into your A(AAA) or PTR records, (e.g., blah.raleigh.nc.us.myfavoriteisp.net)
* Reach out to GeoIP DBs like MaxMind, IP2Location, etc. and submit updates.
Unfortunately, you may have to wait several weeks or even a month for databases to update.
C'est la vie.
Unfortunately, you may have to wait several weeks or even a month for
databases to update.
Don't be silly! It takes nanoseconds to update the database once "the proper motivation" is present to encourage the pressing of the <ENTER> key.
It may take weeks of months for the update to entered into the database, however, once the appropriate motivation is present, the update takes effect immediately. In other words the issue is "motivation" and not a technical one.
"Adequate motivation" is a matter of nuclear weapons, lawsuits, and pending bankruptcy. In the absence of such "motivational factors" there is not impetus to act with expedience.