How To Clean Up Incorrect Geolocation Information?
zorro6 writes "I thought this might be an interesting question/topic and it would sure help me to get some kind of answer. I recently got internet service from a small, local wireless ISP in my area (south central Colorado, USA). The strange thing is that many, many web sites think I am in Quebec, Canada when I use the service. Evidently some geolocation service thinks my IP address indicates I am in Canada. I have checked the obvious. The WHOIS information for my IP correctly indicates a location of Durango, CO. So the bad info is coming from some more sophisticated geolocation service. My ISP is at a loss as to how to fix this but it is causing me a lot of grief. Many of the ads I get shown on Yahoo! for instance are in French! Certain sites won't sell me goods or services because they don't do business in Canada. So far I know that Yahoo! (or their ad provider), Nvidia, Movielink, etc. all think I am in Canada. I would sure appreciate any help/info on how to get this corrected."
Even if you do get the address corrected, it will take years before these companies update their databases and work correctly. About a year ago, the US Post Office changed the zip code in the area that I just moved into, and it has been a hassle left and right.
The electric company claimed they didn't offer service to a house that they were currently providing electricity to. My health insurance was changed to an 'out of area' plan even though my dad already had the right provider in the same zip code. Sears wouldn't deliver until I gave them the old, incorrect zip code. Even Google still has it wrong on some maps, but not others (and I filed the bug months ago, but no fix).
Welcome to another series of problems created by software developers who made bad assumptions.
I agree with this. I've implemented GeoIP on a bunch of sites. Basically, they give you a database linking class A / B / C blocks to certain areas. I don't know where they get this data, but it's what most sites use to determine where you're from. I suggest contacting MaxMind, the maintainers of GeoIP, to correct your information (it's not immediately obvious from their FAQ who you should talk to, but I would start at their contact page). Unfortunately, getting them to make the change may not immediately come into effect on clients' sites... most sites use a static version of the database and update it fairly infrequently (since GeoIP charges for a subscription).
As a side note, I once made an antifraud system on a major unlocked cell phone seller that relied mostly on flagging orders coming from certain countries (using GeoIP) as possible fraud, as well as people who had used the same CC number on more than one account, people who had more than one account in general (using various stats like email address), etc. Seemed to work pretty well for them.
It's better to vote for what you want and not get it than to vote for what you don't want and get it.
- E. Debs
Have your ISP contact Akamai. As an ISP who was also misidentified as "being outside of the USA" by Akamai's geolocation, our customers suffered from the exact same kinds of problems with region protection on network streaming. We didn't get it resolved until we were able to shake the tree properly at Akamai.
AFAIK, Akamai has the most utilized geolocation service out there.
There are two widely used geolocation services which should be your starting point:
MaxMinds and IP2Location.
I would contact them and get them to update their records, especially MaxMind, as they are probably the most widely used geolocation service on the Internet.
I hate printers.
Most of the major Internet companies use Quova (Google, Yahoo, MSN, etc.) for their IP geolocation data (linky. You don't need to have your ISP contact them. Just send an email to support@quova.com with your IP and physical location. They used to provide weekly data updates, so I imagine it is equivalent or more frequent now.
this is all wrong. whois is also used to query the arin database. as the OP stated, this whois information from ARIN is correct.
reverse DNS can not be modified by anyone. only the authoritative nameserver for a region of IP address space (your isp's isp) can delegate that role to another party. this is the essence of the in-addr.arpa domain. most ISPs will not even allow customers with static IP addresses to control the reverse DNS for their addresses.
if you perform reverse dns lookups on the IP addresses appearing near the end of a traceroute you can find useful information for geolocation of the target address. networks generally provide reverse dns for router IP addresses, and those are likely to reveal where the router lives.
Or www.google.com/ncr ... this sets a cookie that prevents further redirects to country-specific sites.
Try going to some other country-specific google url, or going to www.google.com/ncr (No Country Redirect).
most ISPs will not even allow customers with static IP addresses to control the reverse DNS for their addresses.
Dunno what you mean by most or control, but for ATT DSL customers, a call to DNS Provisioning and a day's wait is all that's required. For their part, they basically just create a CNAME record and let you take care of the rest. Unless, of course, you choose to have them take of the rest.