DNS Resolving to wrong address

[pbuko...@gmail.com]

Having an issue where DNS is not resolving correctly over Charter Internet 

DNS not resolving correctly over Charter internet 

Ping: camsbycbs.net - Charter 

IP: 72.233.46.7

Ping: camsbycbs.net - Other ISP 

IP: 173.193.151.230

[Alex Dupuy]

If you can run  dig TXT test.dns.google.com  with either ISP and get a message that mentions Google Public DNS, then it may be related to Google Public DNS (if that ISP is giving incorrect data).  If you can't run that dig command, but can do a dns lookup (with dig or nslookup or even ping) of whoami.akamai.net it will show the resolver that you are using on the two ISPs.  Unless one of them is within the IP address ranges documented at https://developers.google.com/speed/public-dns/faq#locations the problem has nothing to do with Google Public DNS, and you should contact whichever ISP is giving you "wrong" (probably just outdated but not expired) answers.

If the ISP returning incorrect data is using Google Public DNS, you can try flushing the Google Public DNS cache for the camsbycns.net domain: https://developers.google.com/speed/public-dns/cache

Note that flushing the Google Public DNS cache has no direct impact on any caches that an ISP using Google Public DNS may be using, so flushing the cache may or may not solve your problem (it can't really make it worse).

Also, if camsbycbs.net recently changed DNS providers, or is using EDNS Client Subnet for GeoIP resolution, the cache flush will have no effect.

[pbuko...@gmail.com]

I changed DNS on router to 8.8.8.8 and still not seeing correct IP 

[pbuko...@gmail.com]

We have a tier 3 ticket open with the ISP that is causing the problems.  

On Wednesday, January 18, 2017 at 12:49:31 PM UTC-6, Alex Dupuy wrote:

[Alex Dupuy]

The problem with this domain was also reported on our issue tracker, and that was just updated to reflect that the root cause of the problem was an authoritative name server in Toronto not sending the latest version of the zone data. The DNS hosting provider for this domain is working on a resolution, so it should be fixed soon.

[J. Gonzalez]

Alex, thanks for the link to flushing the DNS cache from Google's servers.  We just had an issue where anyone who had configured their computers/servers to use Google's public DNS servers (the .8.8 and .4.4), was getting incorrect IP data from a query.  Everything was correct on our Registrar's DNS servers, and the IP resolved correctly when using DNS query tools, but it wouldn't resolve properly from a computer configured with google's DNS servers.  Once I flushed the cache on their servers, everything started working properly.

Just wanted to say thanks to you and this thread.