Difference Between a Server Outage and a DNS Failure

When a website fails to load in your browser, it is easy to assume "the server is down." In reality, loading a modern web page requires multiple independent systems to succeed in milliseconds. The two most common culprits behind an unreachable website are a DNS Resolution Failure and a Web Server Outage.

Knowing how to tell them apart immediately reveals whether you can fix the issue on your own device (for example, by switching DNS resolvers) or if the website's engineering team is dealing with an infrastructure crash.

1. What Happens During a DNS Failure?

The Domain Name System (DNS) acts as the internet's routing directory. Computers cannot connect to a name like example.com directly; they must first query a DNS resolver to obtain the server's numerical IPv4 (A record) or IPv6 (AAAA record) address.

In a DNS Failure, a resolver cannot provide an address for the browser to use. A cached address or a different resolver may still produce a different result. Common causes include:

• NXDOMAIN (Non-Existent Domain): The domain name is misspelled, expired at the registrar, or its zone file was deleted.
• SERVFAIL (Server Failure): The domain's authoritative nameservers are offline, overloaded, or have a broken DNSSEC cryptographic signature.
• Local ISP Resolver Outage: The website's own DNS is fine, but your Internet Service Provider's default DNS server is failing to resolve queries.

2. What Happens During a Server Outage?

In a possible server or connection outage, DNS may return an address while a subsequent connection or HTTP request fails. An HTTP response from a CDN edge does not necessarily mean its origin application is healthy, and a DNS answer by itself does not prove that the server is reachable.

• Connection Timeout / Refused: The server hardware is powered off, a firewall is dropping incoming packets on port 443, or the web server process (Nginx, Apache, Caddy) has stopped listening.
• CDN Edge Responding, Origin Error (HTTP 502 / 504 / 521): A CDN or reverse proxy may respond even when its upstream origin is unavailable or slow. The response identifies an issue along that request path, not necessarily a complete outage of every part of the site.

3. Quick Comparison Matrix