DNS Not Resolving Troubleshoot: 5 Fixes That Work
Stop guessing. Compare 5 DNS not resolving troubleshoot methods to fix broken lookups fast. Clear steps for hosts and devs.

On this page
TL;DR — Key takeaways
- Check local cache first; flush it before blaming the provider.
- Use dig +trace to identify exactly which nameserver fails the lookup.
- If the domain is new, wait for TTL propagation; do not restart servers.
- Verify A/AAAA records match the actual server IP address.
- If local fixes fail, the issue is likely upstream or at the registrar level.
When a site stops loading, the first instinct is to check the server. But in most support tickets I've handled, the server was fine. The problem was DNS.
This guide compares five practical ways to troubleshoot DNS not resolving issues. We skip the theory and focus on what actually fixes the problem, from local cache clears to upstream provider checks.
Why DNS Fails: The Three Main Layers
DNS resolution happens in three distinct layers. Understanding which layer is broken saves you hours of wasted effort. The first layer is your local device. The second is your ISP or local resolver. The third is the authoritative nameservers for your domain.
Most 'DNS not resolving' complaints are actually local cache issues. Your computer remembers an old IP address for a domain. When the IP changes, your computer keeps trying to connect to the old address. It fails. You think DNS is broken. It's just stale data.
Before you call your hosting provider, you need to isolate which layer is failing. This is where the comparison of troubleshooting methods becomes critical.
- Local layer: Device cache, browser cache, local DNS client
- Resolver layer: ISP DNS, public DNS (8.8.8.8, 1.1.1.1), corporate DNS
- Authoritative layer: Domain registrar, DNS provider, nameserver configuration
Method 1: Flush Local Cache (Fastest Fix)
This is the first step for 80% of cases. It takes 30 seconds. If it works, you're done. If it doesn't, you've ruled out the most common cause.
On Windows, open Command Prompt as Administrator and run ipconfig /flushdns. On macOS, use sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On Linux, it depends on your resolver. systemd-resolved uses systemd-resolve --flush-caches. Unbound uses rndc flush. Check your specific setup.
After flushing, try loading the site again. If it works, the issue was stale local data. If it still fails, move to the next method. Do not restart your computer yet. That's a sledgehammer when you need a scalpel.
- Windows: ipconfig /flushdns
- macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
- Linux (systemd): systemd-resolve --flush-caches
- Linux (Unbound): rndc flush
Method 2: Test with Public DNS (Isolate ISP Issues)
So what if the cache is clean but the site still won't load? Now you need to check if your ISP's DNS servers are the problem. Some ISPs have broken or slow DNS resolvers. Others block certain domains.
Change your device's DNS settings to use a public resolver. Google Public DNS uses 8.8.8.8 and 8.8.4.4. Cloudflare uses 1.1.1.1 and 1.0.0.1. Quad9 uses 9.9.9.9 and 149.112.112.112. Pick one, set it manually, and test again.
If the site loads with public DNS, your ISP's resolver is broken. You have two options: keep using public DNS on that device, or contact your ISP. If it still fails with public DNS, the problem is not your ISP. It's either the domain itself or your local network configuration.
This step is critical because it separates local network issues from domain-level issues. Many support engineers skip this and jump straight to checking server logs. That's backwards.
- Google: 8.8.8.8, 8.8.4.4
- Cloudflare: 1.1.1.1, 1.0.0.1
- Quad9: 9.9.9.9, 149.112.112.112
- If public DNS works, the issue is your ISP resolver
- If public DNS fails, the issue is upstream or local network
Method 3: Use dig +trace to Find the Exact Failure Point
Now we get technical. This is the method that tells you exactly where the lookup fails. It's not as fast as flushing the cache, but it's far more accurate.
Open a terminal and run dig +trace example.com. This command walks the entire DNS hierarchy, starting from the root servers, down to the TLD servers, and finally to the authoritative nameservers for your domain. It shows you every step and every response.
Look for the first line that returns an error or a timeout. If the root servers respond but the TLD servers don't, the problem is at the TLD level. If the TLD servers respond but the authoritative nameservers don't, the problem is with your domain's nameservers. If the authoritative nameservers respond but return NXDOMAIN, the domain doesn't exist or is misconfigured.
This is the most powerful diagnostic tool for DNS issues. It removes all guesswork. You know exactly which server is failing and why. In support tickets, this is the command I ask customers to run before they call me back.
- Command: dig +trace example.com
- Root servers respond? Check TLD servers
- TLD servers respond? Check authoritative nameservers
- NXDOMAIN from authoritative servers means domain doesn't exist
- Timeout from authoritative servers means nameserver is down or unreachable
Method 4: Verify DNS Records and TTL Settings
If dig +trace shows the authoritative nameservers are responding but returning wrong data, the problem is in your DNS zone file. This is where you check the actual records.
Log into your DNS provider's control panel. Look for the A record (IPv4) and AAAA record (IPv6) for your domain. Do they point to the correct IP address? If you recently changed servers, did you update the DNS records? If you're using a CDN, does the A record point to the CDN's IP, not your origin server?
Check the TTL (Time To Live) value. If the TTL is high (like 86400 or 1 week), changes take a long time to propagate. If you just changed the IP, you need to wait for the old TTL to expire. You cannot force this. Lowering the TTL now only helps future changes, not the current one.
Also check for CNAME records. If you have a CNAME pointing to another domain, and that domain is broken, your domain will be broken too. Trace the CNAME chain to find the root cause.
- Verify A record points to correct IPv4 address
- Verify AAAA record points to correct IPv6 address
- Check TTL value; high TTL means slow propagation
- Trace CNAME chains to find broken upstream domains
- If using CDN, ensure A record points to CDN IP, not origin
Method 5: Check Domain Status and Registrar Settings
The last and most overlooked cause: the domain itself. Is it expired? Is it suspended? Are the nameservers configured correctly at the registrar level?
Run whois example.com to check the domain's status. Look for 'expired', 'suspended', or 'clientHold' in the status field. If the domain is expired, no amount of DNS troubleshooting will fix it. You need to renew it first.
Also check the nameservers listed in the whois output. Do they match the nameservers you're using in your DNS provider? If they don't, the authoritative nameservers won't receive queries. The domain will appear broken even if your DNS zone file is perfect.
This step takes 2 minutes. It's the most common cause of 'sudden' DNS failures. A domain expires, the nameservers stop responding, and the site goes down. No error logs. No server issues. Just a lapsed registration.
- Run whois example.com to check domain status
- Look for 'expired', 'suspended', or 'clientHold' status
- Verify nameservers in whois match your DNS provider
- If domain is expired, renew it before troubleshooting DNS
- Registrar-level issues cannot be fixed by changing local DNS settings
Quick troubleshooting checklist
- Flush local DNS cache on the affected device
- Run dig +trace domain.com to isolate the failing nameserver
- Verify A and AAAA records in the DNS zone file
- Check if the domain has expired or been suspended
- Test from a different network to rule out local ISP issues
FAQ
Why does my website load on mobile but not desktop?
This usually indicates a stale local DNS cache on the desktop. Mobile devices often use different DNS resolvers or have shorter cache times. Flush the desktop cache and try again.
How long does DNS propagation actually take?
It depends on the previous TTL value. If the TTL was 3600 seconds, expect up to 1 hour. If it was 86400, expect up to 24 hours. You cannot force propagation faster than the TTL allows.
What does NXDOMAIN mean in dig output?
NXDOMAIN means the domain name does not exist in the DNS hierarchy. This typically happens if the domain is misspelled, not registered, or the nameservers are not configured correctly.
Related articles
- Hosting OperationsDNS Not Resolving: 7 Fixes That Actually WorkFix DNS not resolving errors fast. Compare local, server, and provider-side causes. Get a working checklist for immediate troubleshooting.
- Hosting OperationsDNS Not Resolving Troubleshoot (2026)Compare the main DNS troubleshooting paths, weigh the trade-offs, and pick the right fix for your setup. Follow the steps that actually resolve lookup failures.
- Hosting OperationsWebsite Down Not Working: 5 Fixes That Actually WorkFix website down not working errors fast. Compare DNS, server, and code fixes to restore uptime in minutes.
- Hosting OperationsDNS Not Resolving: 5 Fixes That Actually WorkFix DNS not resolving errors by comparing five practical methods. Identify the root cause and apply the correct solution for your hosting setup.
- Hosting OperationsWebsite Down Not Working: 7 Fixes That Actually WorkFix a website down not working error by checking DNS, disk space, and PHP limits. Stop downtime fast with these 7 practical hosting troubleshooting steps.
- Hosting OperationsWebsite Down Not Working: 7 Fixes That Actually WorkFix a website down not working error fast. Check DNS, server status, and code errors with these 7 practical steps for hosting owners.