Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
Website not showing after DNS redirect and pinging fails
Yesterday I made a nameserver change to make nunoo.dk show a new website that is on my Digital Ocean server. It’s a Nginx + Nodejs setup. The thing is, when I ping www.nunoo.dk it’s actually sending and receiving on the correct IP address (my DO one), but when I ping nunoo.dk (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 www.nunoo.dk.
I’ve checked the nameservers, and they look correct, and also, when I use a DNS tool (https://mxtoolbox.com/Supertool.aspx?action=a:nunoo.dk:all) everything looks OK.
Do I just have to wait, or what should I do 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.×