Skip to main content

  • Home

  • Getting Started

    • Offers

swearmts's profile
swearmts
1st Topic

Visitor

 • 

3 Messages

Thursday, February 9th, 2023 5:15 PM

Closed

IP GEO location has changed after recent infrastructure work in my area

Last week Comcast was in our area doing some type of infrastructure work and notified us our internet would be up and down throughout the week. The work was completed and now our speeds have improved BUT now my IP address is reporting a location of Sacramento instead of the correct Fresno/Merced market. I live in Merced and depend on accurate geo location for my streaming services (i.e. youtube tv). They use the geo location of the IP to put us in the correct market providing us our local channels. Now all our channels (news, etc) and showing Sacramento stations. Sacramento  is more than 2.5 hours north of us. 

I've talked to Support, advance support, onsite tech they dispatch and no one knows what I'm talking about let alone able to help me. They did suggest replacing my modem which I did but the issue persists. 

Please help!

 -Mike [Edited: "Personal Information"]

p.s. releasing & renewing IP has no effect. I think there is something misconfigured with Comcast DNS I've been assigned to use

Question

 • 

Updated 

2 years ago

 • Edited

1.3K

2

0

Was this helpful?

Accepted Solution

EG

Expert

 • 

107.9K Messages

2 years ago

You received a new / different WAN (public) IP address assigned to your connection from their DHCP server / IP address pool, and the rDNS / geolocation data that is associated with it is now incorrect for you as it previously belonged to someone else that lived in that other area. Comcast shuffles blocks of IP addresses around the country all the time. And after doing local plant maintenance / upgrades.

If you are using a router that has a MAC address cloning feature, you can clone a different MAC address into it. This will force a change of your Comcast assigned WAN / public IP address. No guarantees that the new address won't also have incorrect geo-data as it may be from the same block of IP's. YMMV.

 

ISP's don't correct this. A third-party service does. Unfortunately, this is typically a *back-burner* thing to get corrected. The only thing that you can do is to report it. You can try this;


https://www.maxmind.com/en/geoip-location-correction  


http://www.ipligence.com/contact/  


https://www.ip2location.com/contact/  


https://www.home.neustar/contact-us  


https://support.google.com/websearch/contact/ip/  


Wait for the geolocation provider to approve your request. If your request is approved, the amount of time it takes to see the correction varies by provider. The average is a month or more.

(edited)

2

0

swearmts

Visitor

 • 

3 Messages

@EG​ Yeah I saw your other post. And already submitted the adjustment request. The reason I believe this is Comcast is because they moved us to a new block of IP's, which must of originally been used in the Sacramento area. IF they cannot adjust the geo location data then Comcast should at least be able to move us back to the block that was reporting our correct location. This is so very upsetting. The hoops we have to jump through just to get the service I expect and pay for.

Furthermore. This article explains the role a DNS server plays in geo location. Another reason why I think Comcast is at fault. Especially if my DNS lookups are originating on a DNS server located in Sacramento.

How Geolocation DNS Routing Works

When the DNS query arrives on an NS1 nameserver, it is checked to see if the EDNS0 option known as edns-client-subnet is present, and if the record being queried has edns-client-subnet enabled. If both EDNS0 conditions are met, the class C or /24 subnet specified by edns-client-subnet is used. This is the first three octets (111.222.333.xxx) of the real end-user’s public IP address, and allows for much more accurate geolocation targeting.

If the EDNS0 option is not present, or the record being queried does not have edns-client-subnet enabled, the IP address from which the query was received is used. This is typically a caching or recursive resolver, which might not be located anywhere near the actual user. This option will determine the routing based on the location of the recursive resolver and return the appropriate address for that location.

The IP address is looked up in real-time in an IP address-to-location database, which contains base data from MaxMind and undergoes constant refinement and improvement with extensive IP address mapping by NS1. It tells the NS1 resolver the latitude and longitude of the source of the DNS request, either using the EDNS0 option, or the IP address of the recursive resolver.

Next, unless a precise latitude and longitude was assigned to each of the record’s answers, the NS1 resolver uses the latitude and longitude that represents the midpoint of whatever location is assigned to each answer. In other words, if an answer is marked as being in the us-west region, then the geographic center of the western United States is used. On the other hand, if an answer is marked as being in the state of New York, then the latitude and longitude of the exact middle of NY is used.

The distance from the query source IP address’ latitude and longitude to the determined latitude and longitude of each of the answers is calculated in mere microseconds (millionths of a second) and the answers are sorted by decreasing proximity – closest answer on top, and furthest answer on the bottom. If the record is to return only a single final answer, then typically the SELECT_FIRST_N filter is employed to return only the top-most, and in this case closest, answer.

Learn more about geographic routing with NS1.

(edited)

2 years ago

0

swearmts

Visitor

 • 

3 Messages

The more I dig into this the more you appear to be correct. The DNS server I'm assigned to is geo located in Fresno. So I guess I'll just wait and HOPE the that database get's updated. Ugh.. 

 Thanks

2 years ago

0

EG

Expert

 • 

107.9K Messages

2 years ago

@swearmts wrote;

The reason I believe this is Comcast is because they moved us to a new block of IP's, which must of originally been used in the Sacramento area. IF they cannot adjust the geo location data then Comcast should at least be able to move us back to the block that was reporting our correct location.

I wouldn't hold my breath on that one.... Best of luck for a speedy solution !

0

0

forum icon

New to the Community?

Start Here