Troubleshooting

How to fix DNS resolution problems

When your browser says it can't find a server, the problem is either on your side (device, router, ISP resolver) or on the domain's side (missing or broken DNS). This guide helps you tell which — and fix it.

Updated · Published by HostFaddy · 3 min read

See whether the domain resolves for public resolvers

Free, no sign-up — results in seconds.

Step 1: Is it you or the domain?

Run the domain through the DNS checker. If Google, Cloudflare and DNS.SB all return an address, the domain's DNS is fine and the problem is local. If they all return “no record”, the issue is with the domain itself — jump to troubleshooting DNS problems.

Understanding the error messages

ErrorUsually means
DNS_PROBE_FINISHED_NXDOMAINThe resolver says the name doesn't exist — a typo, a missing record, or an expired domain.
ERR_NAME_NOT_RESOLVEDThe lookup failed — no answer, a network problem, or a missing record.
DNS_PROBE_FINISHED_NO_INTERNETYour device can't reach any resolver. Check the connection itself.
SERVFAIL (in dig/nslookup)The resolver couldn't get a valid answer — often broken DNSSEC or unreachable nameservers.

Step 2: Fix it on your device

  1. Flush the DNS cache. Windows: ipconfig /flushdns. macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Linux (systemd): resolvectl flush-caches.
  2. Clear the browser's cache. In Chrome, visit chrome://net-internals/#dns and clear the host cache.
  3. Check the hosts file. An old entry in C:\Windows\System32\drivers\etc\hosts or /etc/hosts overrides DNS completely.
  4. Disable VPNs, proxies or security software briefly to see if they're intercepting lookups.

Step 3: Fix it on your network

  1. Restart the router. Home routers cache DNS and sometimes hang.
  2. Try a different resolver. Temporarily set your device's DNS to a public resolver such as 1.1.1.1 or 8.8.8.8. If that fixes it, your ISP's resolver is the problem.
  3. Test on another network (mobile data). If it works there, the issue is on your network or ISP.

Step 4: If public resolvers fail too

Then it's the domain, not you. Common causes: the domain expired, nameservers are misconfigured, the record was deleted, or DNSSEC is broken. Check the NS records, use the All DNS Records lookup, and confirm the domain's registration status with a WHOIS lookup.

Frequently asked questions

Is it safe to use 1.1.1.1 or 8.8.8.8?

Yes, they're widely used public resolvers. Read each provider's privacy policy and choose the one you're comfortable with.

Why does only one website fail to load?

That domain's DNS is probably at fault, or your device has a stale cache entry or hosts file entry for it.

Flushing DNS didn't help — what next?

Try another network. If it works elsewhere, change your resolver or contact your ISP; if it fails everywhere, the domain itself has a DNS problem.