DNS 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.

On this page
TL;DR — Key takeaways
- Start with a single DNS query from the client machine to isolate whether the failure is local, network-level, or authoritative.
- Check the local resolver cache, ISP DNS, and public resolvers in that order before touching server configuration.
- Verify that the authoritative nameservers match the registrar and that the zone file contains the correct A, AAAA, and MX records.
- Use TTL values as a buffer for changes, but remember that low TTLs do not speed up propagation once the resolver cache is warm.
- Compare public resolvers, local resolvers, and authoritative checks to pinpoint where the lookup breaks before applying any fix.
- Keep a rollback plan for DNS changes, and test with a secondary resolver before declaring the issue resolved.
DNS failures usually follow a clear path: the client asks, the resolver answers, the authoritative server confirms. When one link breaks, the site stays unreachable.
This guide compares the main troubleshooting paths, weighs the trade-offs, and gives you a practical way to isolate the failure without guessing.
Where the DNS lookup actually breaks
DNS resolution involves three layers: the client resolver, the recursive resolver, and the authoritative nameserver. A failure at any layer stops the lookup.
Start by confirming the failure point. Run a query from the client machine, then from a different network, and finally from a public resolver. If the lookup works from a public resolver but fails locally, the issue is likely local cache, firewall, or network routing.
If the query fails from the public resolver too, the problem sits at the authoritative nameserver or in the zone configuration. This split test saves hours of guessing.
- Client resolver: local cache, OS settings, and browser behavior
- Recursive resolver: ISP, public DNS, or corporate DNS
- Authoritative server: nameserver delegation, zone file, and record syntax
Compare the main troubleshooting paths
You can fix DNS issues by working locally, by changing resolver settings, or by editing the authoritative zone. Each path has a different risk profile and a different verification step.
Local fixes are safe and reversible. Flush the cache, restart the resolver service, or switch to a public DNS. These changes do not affect your domain or your visitors.
Authoritative changes are riskier. Editing nameservers, TTL values, or zone records can affect the whole domain. Always keep a backup of the previous zone file and test with a secondary resolver before applying the change.
- Local troubleshooting: safe, fast, and reversible
- Resolver switching: useful for isolating ISP or corporate DNS issues
- Authoritative changes: powerful but require rollback planning
When to check the local cache and OS settings
The local cache is the first place to look. A stale entry can return an old IP address even after the zone file changes. Flush the DNS cache on the client machine, then retry the lookup.
On Windows, use ipconfig /flushdns. On macOS, run sudo dscacheutil -flushcache. On Linux, the command depends on the resolver, but systemd-resolved and nscd both support a flush command.
Check the network adapter settings as well. A static DNS entry that points to a dead IP will fail just like a misconfigured zone. Compare the configured DNS servers with the ones your network actually uses.
- Flush the local cache and restart the resolver service
- Verify the configured DNS servers match the network gateway
- Test with a different network to rule out local routing issues
How to verify the fix and when to roll back
Verification is a three-step process. First, confirm the lookup works from a public resolver. Second, confirm the same result appears from a different network. Third, confirm the site loads in a browser after the DNS change.
If the change does not resolve the issue, roll back to the previous zone file or nameserver configuration. Keep a backup of the old file and restore it within minutes if the problem persists.
Document the change, the TTL value, and the verification result. This record helps you spot patterns and avoids repeating the same mistake on the next incident.
- Verify from a public resolver, a different network, and a browser
- Keep a backup of the previous zone file and rollback if needed
- Document the change, TTL, and verification result
Quick troubleshooting checklist
- Run nslookup or dig from the client machine to confirm the failure point
- Flush the local DNS cache and retry the lookup
- Check the ISP DNS and a public resolver like 8.8.8.8 or 1.1.1.1
- Verify the registrar nameservers match the authoritative nameservers
- Inspect the zone file for missing, duplicate, or malformed records
- Confirm the TTL value and allow time for resolvers to refresh
- Test with a secondary resolver before declaring the issue resolved
- Keep a backup of the previous zone file and rollback if needed
FAQ
Why does DNS not resolve for my website?
DNS does not resolve when the client cannot reach a working resolver, the resolver cannot find the authoritative zone, or the zone file lacks the correct record. Common causes include a misconfigured local cache, ISP DNS issues, wrong nameserver delegation, or a missing or malformed A or AAAA record.
How long does DNS propagation take?
DNS propagation is not a single event. It depends on the TTL value set on the record, how long resolvers have cached the old value, and how quickly each recursive resolver updates its cache. Most changes settle within a few hours, but some resolvers may hold stale data for up to 48 hours.
Which DNS resolver should I use for testing?
Use a public resolver like Google DNS 8.8.8.8 or Cloudflare 1.1.1.1 for initial testing, then compare the result with your local resolver and the authoritative nameserver. If all three return the same answer, the issue is likely local or application-level rather than DNS.
Related articles
- Hosting OperationsDNS Not Resolving Troubleshoot: 5 Fixes That WorkStop guessing. Compare 5 DNS not resolving troubleshoot methods to fix broken lookups fast. Clear steps for hosts and devs.
- Hosting OperationsDNS Not Resolving: Step-by-Step FixDNS not resolving? Compare common causes, test with real commands, and apply the right fix for your setup. Follow this evergreen troubleshooting guide.
- Hosting OperationsHow to fix dns not resolving ip address: Practical GuideStep-by-step guide to diagnose and fix DNS resolution failures. Learn safe troubleshooting methods to restore name resolution quickly.
- Hosting OperationsDNS Not Resolving Error — 7-Step Fix (2026)Fix DNS not resolving error with a 7-step checklist. Audit, harden, and verify your DNS configuration for 2026 security.
- 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.