Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Unable to access my server
I'm in Las Vegas and my server is located in Orlando. Today, I started receiving errors indicating:
ERR_NAME_NOT_RESOLVED
After consulting for a few hours with my web host, they have determined that the issue lies with the ISP, as the server is accessible via:
1) A proxy
2) A wifi connection
3) A wireless data connection
But only for others who are not using my account with Cox.
There was a very detailed explanation about what was most likely happening, but I don't want to post everything in a public forum. The gist of it, through multiple verified sources, is that all tests and results are pointing towards:
"ISP-level DNS caching being the culprit"
Can you tell me how long it will be until I'm able to see my server again?
Health_Edge
+5 more
Valued Contributor III
•
Whats the domain? If you just set up the DNS for the domain, it will probably take a day or two for the DNS to propagate/filter through the different parts of the DNS system. Some of it will depend on what you have your TTL set for your A record. As a work around until Cox DNS updates, you can try using a 3rd party DNS like Google (8.8.8.8/8.8.4.4) to see if that may already be updated.
You can also check the "ISP Cached DNS Lookup" on this page. I can give specifics, but I would need to know the domain/server.
0
0