DNS TROUBLESHOOTING GUIDE
How to Fix DNS Server Not Responding on Windows and Mac
A DNS resolver helps translate a website’s hostname into the address your device needs to connect. If your device cannot obtain a usable DNS answer, websites may fail to load even while Wi-Fi or Ethernet shows an active connection. “DNS Server Not Responding” points to a lookup problem, but it does not establish that the resolver itself is down.
Start by finding out whether the failure affects one website, one device, or an entire network. Then compare your configured resolver with another resolver where network policy permits. This guide explains what to check on Windows and macOS before making broader changes.
Start here
Try another website and device, restart the browser, check the connection, and compare another network. Test DNS with nslookup or dig. Clear a stale local cache if appropriate, review DNS settings, and investigate VPN or router behavior before considering an advanced network reset.
What Does “DNS Server Not Responding” Mean?
The device or application cannot obtain a usable DNS response through its configured lookup path. The problem may be an unavailable resolver, an unreachable network route, a router’s DNS forwarder, or an incorrect DNS address. The message is a starting point for diagnosis rather than a precise server-health report.
Other causes include VPN DNS overrides, proxy configuration, security software or firewall rules, local DNS cache problems, and adapter or network configuration errors. A connection indicator confirms a network link; it does not prove that the internet, DNS, and the website are all reachable.
NXDOMAIN is different: it can be a valid DNS response saying that the queried name does not exist in the data available to the resolver. Receiving NXDOMAIN means a DNS answer arrived, although the underlying hostname or DNS setup may need correction. A timeout means no answer arrived within the test’s waiting period.
Quick Troubleshooting Checklist
1. Try another website
If unrelated websites work, focus on the failing hostname or service rather than assuming all DNS is broken. If many unrelated names fail, the shared resolver or network path is more likely to be involved.
2. Check another device
Test the same hostname on a second device using the same network. One failing computer points toward its own browser, cache, VPN, or adapter settings; several failing devices point toward shared network conditions.
3. Restart the browser
Fully close and reopen it, then compare another browser. If only one browser fails, check its Secure DNS and proxy settings. A private window alone does not necessarily bypass browser-managed DNS caches.
4. Check the network connection
Confirm you are connected to the intended Wi-Fi or Ethernet network and complete any captive-portal sign-in. Check for a reported internet outage rather than treating a Wi-Fi signal as proof of internet access.
5. Restart the router if appropriate
If several devices on your own network fail, an ordinary router restart may clear temporary forwarding state. Avoid disrupting essential work. A restart is different from a factory reset and does not repair a domain’s authoritative records.
6. Try another network
Compare a trusted alternative, such as mobile data. A site that works elsewhere suggests a problem specific to the original network, resolver, or filtering policy. Consider mobile data charges and workplace requirements.
7. Test DNS directly
Use nslookup or dig to compare the default resolver with an explicitly chosen public resolver. Keep the exact status and output; it is stronger evidence than a generic browser error.
Fix DNS Server Not Responding on Windows
Method 1: Restart the network connection
Disconnect and reconnect Wi-Fi using the network menu. For Ethernet, reconnect the cable or briefly disable and re-enable the active adapter if it is safe to do so. This interrupts your connection, so avoid doing it during important transfers or a remote-support session. Retest before changing additional settings.
Method 2: Flush the DNS cache
Open Command Prompt from Start. Choose Run as administrator if your Windows configuration requires it, then run:
ipconfig /flushdnsThe command removes entries from the local Windows DNS resolver cache, including cached failures. It does not repair wrong authoritative records, fix an unreachable resolver, or clear caches at your ISP, router, or every browser. Reopen the browser and retest the affected hostname.
Method 3: Check DNS server settings
Review the active network adapter, not an unused adapter. On Windows 11, look under Settings → Network & internet → your Wi-Fi or Ethernet connection → DNS server assignment. On Windows 10, use the adapter’s IPv4 properties. Interface labels vary by version. Note whether DNS is assigned automatically and record any manual addresses before changing them.
First compare an alternate resolver using a command-line query rather than changing the whole device. If that test works and your current resolver consistently fails, an unmanaged home connection may benefit from a temporary test with a trusted public resolver:
Resolver
DNS server addresses
Cloudflare
1.1.1.1
1.0.0.1
Google Public DNS
8.8.8.8
8.8.4.4
Record the original settings and restore them if the test does not help. Changing DNS providers is not automatically the right permanent solution. Corporate networks, Active Directory, VPNs, private domains, and managed devices may require organization-specific DNS. Public DNS can break those lookups or bypass intended filtering; consult the administrator before changing a managed configuration.
Method 4: Consider network-component resets only when justified
If the failure remains specific to this Windows device after resolver and connectivity checks, damaged network components may need further investigation. A Winsock reset is a more invasive troubleshooting step, not a routine DNS-cache flush. It requires an elevated Command Prompt and usually a restart; it can affect networking software or require follow-up configuration.
netsh winsock resetUse this only with a clear reason or support guidance, and preserve relevant network and VPN configuration first. The broader Windows Network reset option can remove and reinstall adapters and may require VPN or static-address reconfiguration. Do not reset adapters, firewall settings, or the TCP/IP stack simply because one domain returns a DNS error.
Fix DNS Server Not Responding on macOS
1. Check and reconnect the active connection
Confirm that Wi-Fi or Ethernet is connected and other sites are reachable. Disconnect and reconnect the active network where appropriate, complete any sign-in portal, and restart the affected browser. Avoid interrupting remote access or other essential work.
2. Review DNS settings
On recent macOS versions, open System Settings → Network → the active connection → Details → DNS. Older versions use System Preferences → Network → Advanced → DNS. Check for unexpected manually configured addresses and whether a VPN supplies its own DNS. Preserve the original configuration.
If comparisons indicate a resolver-specific problem and network policy allows it, temporarily test Cloudflare or Google Public DNS using the addresses above. Keep organization-specific settings for managed networks and private domains. Restore the original configuration if the test does not help.
3. Flush a stale local DNS cache when appropriate
On many modern macOS versions, open Terminal and run the following example. Enter your administrator password when prompted; the characters are not displayed.
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderExact behavior can vary by macOS version, and successful execution may produce no confirmation message. Use version-specific guidance if the commands are unavailable. They refresh local lookup state, not ISP or public resolver caches.
4. Restart affected applications and retest
Reopen the browser and compare its behavior with a command-line lookup. Browser DNS-over-HTTPS can use a separate resolver, so a successful macOS lookup does not rule out a browser-specific setting. Reconnect the network only when the evidence points to that connection; avoid unrelated system changes.
How to Test Whether DNS Is Working
Use the same hostname for each comparison. Replace example.com with the affected name, without https:// or a path. For a network-wide problem, also test a known unrelated hostname rather than drawing conclusions from one website.
Windows: compare the default and an alternate resolver
nslookup example.comnslookup example.com 1.1.1.1
The Server shown near the top is the resolver being queried, not necessarily the website’s server. “Non-authoritative answer” is normal for many recursive responses and does not mean the result is incorrect. These lookup commands generally do not require administrator access.
macOS and Linux: use dig where available
dig example.comdig @1.1.1.1 example.com
dig is available on many macOS and Linux systems, but some environments require the distribution’s DNS utilities package. nslookup is an alternative where installed. Direct queries to external DNS servers may be restricted by your network.
Successful responses
A valid answer with the expected records shows that the tested DNS path worked at that moment. With dig, inspect the status and ANSWER SECTION. NOERROR with no records can mean the name exists but lacks the requested type; it is not automatically an outage. Successful DNS does not prove that the web server, TLS certificate, or application is healthy.
Timeouts
No usable response arrived before the tool’s timeout. Possible causes include a resolver outage, blocked DNS traffic, routing problems, or connectivity loss. Compare another permitted resolver and network; a timeout alone does not identify which component failed.
SERVFAIL
The resolver replied that it could not complete the lookup. Causes can include DNSSEC validation failures, broken delegation, or unavailable authoritative servers. It is different from receiving no response and does not prove a general resolver outage.
NXDOMAIN
The resolver answered that the queried name does not exist in the available DNS data. Check spelling, the exact subdomain, authoritative records, and cached negative answers rather than resetting a working network connection.
Different results from different resolvers
If the default resolver fails while an alternate succeeds, investigate the default resolver or the path to it. Differences can also be intentional on private networks, or reflect caching and filtering. If multiple resolvers fail only for one domain, investigate that domain. A couple of tests do not establish the status of every resolver worldwide.
Check Your Domain's Public DNS Records
Hostingcone’s DNS Lookup Tool can check public A and AAAA addresses, CNAME aliases, MX mail routing, TXT verification or authentication values, and NS records. Query the exact hostname and compare the returned values with the hosting or email provider’s required configuration.
A successful public lookup helps separate a public-domain problem from a device-specific problem, but it does not directly diagnose every local computer, router, VPN, or ISP fault. The tool checks public records and selected common hostnames, not every record in a DNS zone or every resolver worldwide. Private DNS may legitimately differ from public answers.
DNS Errors Caused by Your Router or ISP
Router forwarding and DNS settings
Some devices send DNS queries to the router, which forwards them upstream. An incorrect upstream address or temporary forwarding problem can affect every connected device. On a router you manage, review the configured DNS service and compare a permitted direct query with a router-mediated one. Save the current configuration before making a targeted change.
ISP resolver outages and captive portals
If several unrelated names fail through the ISP resolver but work through another permitted resolver or network, check the ISP’s service notices and contact support. On hotel, guest, or public Wi-Fi, complete the captive-portal sign-in first. Substituting public DNS may not bypass network restrictions or a connection that lacks internet access.
VPN overrides, proxies, and firewall rules
VPNs can route DNS to private resolvers, and browser Secure DNS may send queries elsewhere. Proxy settings, endpoint security, or firewall rules may also interfere with the lookup path. Compare settings with the network’s expected configuration. If allowed, briefly test without an optional VPN and then restore it; do not disable required protection or remove firewall rules indiscriminately.
An ordinary restart of your own router may help a temporary fault, but a factory reset erases configuration and should not be an initial step. For a managed router or workplace network, gather test results and involve the administrator rather than changing shared settings.
When the Problem Is With Your Domain
When many users or independent networks fail only for your domain, inspect the domain’s authoritative DNS and registration status. Device cache flushes cannot correct records saved in the wrong zone.
Verify the registrar’s assigned authoritative nameservers and edit the DNS zone they actually serve. Changes made at an inactive hosting account or previous DNS provider will not appear in public answers. Check the exact hostname, A and AAAA addresses, and CNAME targets; a root domain working does not guarantee that www is configured.
Confirm that the domain has not expired, been suspended, or been placed on a status that affects DNS. Handling varies by registrar and registry. If validating resolvers return SERVFAIL after a DNS-provider move, ask the provider to check the DS/DNSKEY chain for a DNSSEC mismatch rather than disabling DNSSEC blindly.
Compare authoritative answers with recursive results. If the source is correct but some cached answers are old, TTLs, negative caching, and delegation caches may explain differences. If authoritative answers are wrong, waiting for an arbitrary propagation period will not fix the configuration.
When to Contact Your DNS Provider
Contact the ISP or network administrator when several devices cannot reach the configured resolver. Contact the registrar or authoritative DNS provider when nameservers, domain status, records, or DNSSEC are incorrect. Persistent timeouts or SERVFAIL across independent tests deserve investigation, but the provider responsible depends on where the lookup fails.
Include the affected hostname, time of the issue, devices and networks tested, default and alternate resolver results, and any recent DNS or hosting changes. Redact private details and do not share passwords, API keys, private keys, or account recovery codes in an ordinary support request.
Hostingcone’s published DNS Fixes service is $79 one-time for one domain and includes up to 1 hour of standard DNS troubleshooting and configuration. Additional work requires approval. Review the current service page for scope and exclusions; it is not a guarantee that every device, ISP, or application problem can be repaired within that service.
Frequently Asked Questions
Why does my computer say DNS server not responding?
It cannot obtain a usable DNS answer through the configured lookup path. Possible causes include resolver availability, connectivity, router forwarding, DNS settings, VPN behavior, or local configuration. The message alone does not identify the failed component.
Can I have internet access but DNS still fail?
Yes. Some established connections or cached names can work while new DNS lookups fail. A Wi-Fi or Ethernet indicator also confirms only the local connection, not that DNS and every internet service are reachable.
Does flushing DNS fix the problem?
It can help when a local cache contains an outdated or failed answer. It cannot repair an unreachable resolver, wrong authoritative records, or a remote provider’s cache. Retest to see whether it changed the result.
Is it safe to use Cloudflare or Google DNS?
They are widely used public resolvers, but suitability depends on your privacy preferences and network requirements. Managed networks, VPNs, and private domains may require specific DNS. Test only where permitted and keep the original settings.
How do I know whether my DNS server is down?
Compare several unrelated names through that resolver, then test another permitted resolver and network. Consistent failure narrows the possibilities but can still reflect a blocked route or local firewall. Check provider status information before declaring an outage.
Why does DNS work on my phone but not my computer?
The devices may use different resolvers, caches, VPNs, or browser settings. The phone may also be using mobile data rather than the same Wi-Fi. Compare both devices on the same network first, then investigate the computer’s configuration.
Can a VPN cause DNS errors?
Yes. A VPN can supply a private resolver or change DNS routing. Incorrect configuration or an unreachable VPN resolver can prevent lookups. Do not replace required corporate DNS with public DNS without administrator guidance.
What is the difference between DNS timeout and NXDOMAIN?
A timeout means no usable response arrived within the waiting period. NXDOMAIN is a received DNS response indicating that the queried name does not exist in the available data. They call for different troubleshooting paths.
Should I reset my router to fix DNS problems?
An ordinary restart may help a temporary problem affecting multiple devices. A factory reset is much more disruptive and should not be the first action. Review DNS settings, test another network, and consult the ISP or administrator when appropriate.
Still Having DNS Problems?
Check your domain's DNS records with Hostingcone's free lookup tool, or get assistance troubleshooting DNS configuration problems.
Explore more DNS troubleshooting guides and tools in the Hostingcone DNS Troubleshooting Hub.