DNS troubleshooting checklist
These browser errors mean your computer couldn’t find your domain in DNS:
DNS_PROBE_FINISHED_NXDOMAIN- “This site can’t be reached. Server IP address could not be found”
- “Hmm. We’re having trouble finding that site”
ERR_NAME_NOT_RESOLVED
Work through this checklist.
1. Is it just you?
Section titled “1. Is it just you?”Open the site on your phone using mobile data, or ask someone elsewhere to try. If it works for them, the problem is your network or computer:
- Clear your DNS cache and restart your browser. See DNS propagation explained.
- Restart your router.
- Disable any VPN, or switch your DNS to a public resolver such as
1.1.1.1or8.8.8.8.
2. Is the domain active?
Section titled “2. Is the domain active?”In the client area, check that the domain’s status is Active and it hasn’t expired. An expired or suspended domain stops resolving. See Renewing an expired domain and ServerHold and ClientHold explained.
3. Are the nameservers right?
Section titled “3. Are the nameservers right?”Check the domain’s nameservers. For Ruachost hosting they should be nsa.ruachost.com and nsb.ruachost.com. See Checking a domain’s WHOIS and nameservers.
If you changed them in the last 48 hours, the change may still be spreading.
4. Does the record exist?
Section titled “4. Does the record exist?”Look for an A record for @ (and a record for www) in the client area DNS Manager or cPanel’s Zone Editor. If it’s missing, add it. See Managing DNS records.
5. Is DNSSEC set up correctly?
Section titled “5. Is DNSSEC set up correctly?”If you recently moved the domain or changed nameservers while DNSSEC was on, the old signatures can break DNS. Turn DNSSEC off, or open a support ticket. See How to enable DNSSEC.
Other errors
Section titled “Other errors”- The site loads, but shows the wrong website or a parking page: see I registered a domain but my website isn’t showing.
- Only
www(or only the domain withoutwww) fails: see My domain works without www but not with it. - Changes you made aren’t showing: see My DNS changes aren’t working.
For advanced checks with command-line tools, see Troubleshooting DNS with dig and nslookup.