Website not showing after DNS redirect and pinging fails


Yesterday I made a nameserver change to make show a new website that is on my Digital Ocean server. It’s a Nginx + Nodejs setup. The thing is, when I ping it’s actually sending and receiving on the correct IP address (my DO one), but when I ping (without www) the request timeouts and the IP is an old one.

I’ve created A records for both with and without www, and I’ve also redirected www. to non-www via Nginx.

The website is showing an old one. But - before I made the www to non-www redirect in Nginx, I could get the new website to show by using

I’ve checked the nameservers, and they look correct, and also, when I use a DNS tool ( everything looks OK.

Do I just have to wait, or what should I do now?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Accepted Answer

This sounds to me like you were experiencing some odd results while your changes propagated. DNS resolvers used by ISPs cache results for a while so they don’t have to go back to query the authoritative nameserver for every request and while this is usually not too long during the time when your ISP has an older record and when it updates to fetch the new one you may see some issues like this.

My own testing shows your site working properly both with and without the www at this time.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.