DNS won't resolve on main domain name?


Tonight I started messing around with a new server, and switched my main domain name over to the new IP and everything seemed to work fine. Then, the main domain name stopped working (Chrome says ERR_NAME_NOT_RESOLVED). Subdomains still worked, and my webmin still worked (on port 10000) but I can’t get to anything on the main domain. Tired of fussing with it, I delete that record in the Digital Ocean control panel and create a new entry for the original server, which hasn’t been touched. Now it too doesn’t work on the main domain name. Again, my control panel (vestaCP) and subdomains work, but the main site produces a DNS error. Any idea what might be causing this?

Domain name: Test server IP: Original IP:


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

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.

That did it - wow. Thanks! What a weird thing.

It appears that is resolving but the web server at is redirecting requests to There does not appear to be an A or CNAME record created for

Assuming you are using the default settings in the DigitalOcean control panel for DNS and have an A record created for “@” which points at your droplet’s IP address you should just need to create a CNAME record pointing to that record:

www    CNAME    @