A "DNS Server Unavailable" error on one website means your device could not look up that site's address, while other sites still resolve normally. DNS, the Domain Name System, is the lookup service that turns a domain name into the numeric IP address a browser needs to connect.
That split result is normal. Browsers, routers, and providers cache past lookups, and each domain can use different name servers. So one broken link in that chain can block a single site without breaking the rest of the web.
Table of Contents
- Why one site fails while others load
- The most common causes for a single-site DNS failure
- Is the problem yours or the site's?
- What to do as a visitor
- What to check as a site owner or manager
Why one site fails while others load
Your computer asks a resolver, usually run by your internet provider or a public service, for each new domain. If the resolver has a fresh cached answer for other sites, those sites open at once. The failing site needs a new lookup, and that fresh lookup is the one hitting trouble.
A domain also depends on its own authoritative name servers. Those are the servers that hold the official address records for that domain. If they are down, misconfigured, or unreachable from your network, only that domain fails.
The most common causes for a single-site DNS failure
Expired, missing, or wrong DNS records are a frequent cause. Common examples are a changed web host without an updated A record, a lost CNAME entry for "www", or broken name-server delegation after a domain move. Visitors then get a DNS error even though the website files are fine.
Local problems can copy the same pattern. A stale record in your system cache, a bad entry in a hosts file, a router glitch, VPN filtering, or browser DNS prefetching can block one domain. Provider resolvers can also have partial outages or aggressive filtering that affects only certain domains.
Is the problem yours or the site's?
Check the same address on another network, such as mobile data with Wi-Fi off. If it loads there, the issue is likely your device, router, VPN, or current resolver. If it fails everywhere, the issue is likely the domain's DNS setup.
Site owners and managers can run one more check. Ask a colleague in another city or use a global DNS checker to query the domain from several locations. Failure in many places points to the authoritative DNS or domain registration, not to one visitor's connection.
What to do as a visitor
Start with the least disruptive steps. Reload after a minute, open the page in a private window, try the version with and without "www", and restart your router if other new sites also feel slow.
Stop after those steps if the site still fails. The next fix usually belongs to the site owner, and repeated setting changes on your side will not repair a broken authoritative record.
- Flush local DNS cache, then clear the browser cache
- Turn off VPN, ad filtering, or custom DNS temporarily and retest
- Change resolver to a major public resolver, then change back after testing
- Try another device on the same network to isolate device versus router
What to check as a site owner or manager
Confirm the domain is active, unlocked, and pointed at the correct name servers at the registrar. Then check the DNS zone itself: A and AAAA records for the root domain, CNAME or A record for "www", MX records left intact, and a reasonable TTL, the lifetime that tells resolvers how long to cache each answer.
Watch for recent changes. A host migration, HTTPS redirect rule, content delivery setup, or WordPress and Drupal domain move can leave mixed addresses behind. Keep old records until the new TTL has expired everywhere, test both HTTP and HTTPS forms, and ask affected users for their error text, location, and provider to speed up support.
