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
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 ERRNAMENOT_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: blueleafweb.com
Test server IP: 184.108.40.206
Original IP: 220.127.116.11
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.×