Have a site on Digital Ocean so the DNS at godaddy is pointed to ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com

On Digital Ocean->Networking->domains
A domain.com routes to 134.xxx.xxx.xxx
A www.domain.com routes to 134.xxx.xxx.xxx

NS domain.com directs to ns1.digitalocean.com
NS domain.com directs to ns2.digitalocean.com
NS domain.com directs to ns3.digitalocean.com

The server block is located in
/etc/nginx/conf.d/domain.com

When my business partners in NYC on a verizon network do a traceroute it ends up at a 198.xxx.xxx.xxx
When I do a traceroute on Cox network in middle America I get it going to 134.xxx.xxx.xxx

Any ideas why in a different area of the country it won’t resolve. We’ve had the domain set up for over a week now.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer

Hi there @austinCoral,

This sounds like DNS caching, note that once you make a DNS change it could take up to 24-48 hours for the DNS cache to clear over the Globe before you could see the new changes.

Hope that this helps!
Regards,
Bobby

Submit an Answer