DNS Server Not Responding: Causes, Fixes, and Prevention Guide.

You’re trying to load a website, but nothing happens. Maybe it spins forever, maybe you get a cryptic error. You check your internet, and everything else seems fine. 

The culprit? Often, it’s a DNS server not responding. 

This issue can crop up out of nowhere and bring your workflow to a halt, especially if you’re managing infrastructure, running a digital business, or supporting customers. DNS problems can look like network outages, but they’re often fixable with a few smart steps.

Knowing how to identify and resolve them quickly can save hours of downtime and frustration. Stick with us and you’ll learn how to diagnose and fix DNS server issues fast.

Key takeaways

• Understand what a “DNS server not responding” error really means
• Learn beginner and advanced DNS troubleshooting steps
• Fix DNS issues across Windows, macOS, and mobile devices
• Choose faster, more reliable DNS servers
• Prevent future DNS disruptions with proactive settings

Don’t wait until your DNS fails.

Set up UptimeRobot’s DNS Monitoring to detect DNS outages instantly & before users notice.

Downtime happens. Get notified!

Join the world's leading uptime monitoring service with 2.1M+ happy users.

Register for FREE

What does “DNS server not responding” mean?

When you see the error “DNS server not responding,” your device is telling you it can’t reach the system that translates domain names (like example.com) into IP addresses. 

Without this translation, your browser doesn’t know where to send your request, so websites won’t load. This issue can affect a single site or your entire internet connection, depending on the cause.

How DNS works behind the scenes

DNS, or Domain Name System, is like the internet’s phonebook. When you type a URL into your browser, your device asks a DNS server to find the matching IP address. If the DNS server doesn’t respond, the request times out, and your browser shows an error.

Here’s a simplified flow:

1. You enter www.example.com in your browser.
2. Your device checks its local DNS cache.
3. If no match is found, it queries the configured DNS server (often your ISP’s).
4. The DNS server returns the IP address.
5. Your browser connects to the site.

If step 3 fails because the DNS server is down, unreachable, or misconfigured, you’ll get the “DNS server not responding” error.

What the error actually means

This error doesn’t always mean the DNS server is down. It could also mean:

• Your device can’t reach the DNS server due to a network issue.
• The DNS server is overloaded and ignoring requests.
• Your firewall or antivirus is blocking DNS traffic.
• You’ve manually set an invalid DNS server in your network settings.

For example, if you switch from automatic DNS to a custom one like 1.1.1.1 (Cloudflare) and mistype it, your device won’t be able to resolve domains. The server isn’t responding because it doesn’t exist at that address.

Temporary vs persistent DNS issues

Some DNS errors are short-lived. A brief network hiccup, a router reboot, or a temporary outage on your ISP’s end can trigger the message. Others are persistent and require manual fixes.

Here’s how to tell the difference, along with some quick fixes:

Knowing which type you’re dealing with helps narrow down the next steps.

Before diving into solutions, it helps to understand what causes these errors in the first place.

Common causes of the error

A “DNS server not responding” message can stem from several underlying issues; sometimes on your device, sometimes on your network, and occasionally with your DNS provider itself. 

Here are the most common reasons this error appears.

1. Misconfigured network or DNS settings

If your device is using the wrong DNS server address or a static IP that no longer exists, it won’t be able to resolve domains. This often happens after switching networks, installing VPN software, or manually entering DNS addresses.

2. DNS server outages or high latency

Even reliable public DNS providers like Google (8.8.8.8) and Cloudflare (1.1.1.1) can experience slowdowns or outages. When a DNS server is overloaded or temporarily unreachable, your browser times out while waiting for a response.

3. Router or modem issues

Routers act as intermediaries for DNS queries. When they overheat, crash, or use outdated firmware, DNS requests may not leave your local network. Stale DNS cache on the router can also trigger repeated lookup failures.

4. Firewall, VPN, or proxy interference

Firewalls and VPNs sometimes block or reroute DNS traffic. Overly strict security software can mistakenly classify DNS lookups as unsafe, while misconfigured VPNs and proxies may prevent queries from reaching your provider.

5. Browser or operating system cache conflicts

Your browser or OS stores DNS records to speed up browsing, but cached entries can become outdated. If a site’s IP address changes, your device may still try to reach the old one, leading to failed connections.

6. IPv6 configuration problems

Dual-stack networks that support both IPv4 and IPv6 can encounter DNS timeouts if IPv6 is enabled but not configured correctly. The device keeps trying the IPv6 path even when it’s nonfunctional.

7. Malware or modified hosts file

Certain types of malware alter your DNS settings or modify your hosts file to redirect traffic. This can break normal resolution or send your requests to malicious servers instead.

8. ISP-level problems or hijacking

Sometimes the issue isn’t on your end. ISPs can experience DNS outages or intercept failed lookups for ad injection or filtering. If this happens, every device on the network will show the same error.

Quick fixes for beginners (simple first steps)

You don’t need deep technical knowledge to solve most “DNS server not responding” errors. Many are caused by small, temporary issues that you can fix in a few minutes.

Start with these quick, low-effort checks before moving on to advanced troubleshooting.

1. Restart your router and computer

This simple step fixes a surprising number of DNS problems. Restarting your router resets the network connection and clears temporary issues that may block DNS queries.

1. Turn off your router and modem, then unplug them for 30 seconds.
2. Restart your computer or device while they’re unplugged.
3. Plug the router and modem back in and wait for them to fully reconnect.

Once everything is back online, test a few websites to see if the issue is gone.

2. Try a different browser or device

If the problem only appears in one browser or device, it’s likely not your DNS server.

1. Open the same site in another browser (for example, try Firefox instead of Chrome).
2. If it loads fine, clear your browser cache or reset its settings.
3. If the error appears across multiple browsers or devices, the issue is network-wide.

This quick comparison helps rule out browser-level caching or local misconfigurations.

3. Flush your DNS cache

Your operating system stores DNS entries locally. If those records become outdated or corrupted, your device may fail to connect. Clearing the cache forces a fresh lookup.

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux (systemd):

sudo systemd-resolve --flush-caches

After flushing, reopen your browser and try again.

4. Switch to a public DNS server

Your ISP’s DNS servers can occasionally be slow or unreliable. Public DNS providers like Google (8.8.8.8), Cloudflare (1.1.1.1), or Quad9 (9.9.9.9) often respond faster and with fewer errors.

You can change DNS settings on your device or router:

• Windows: Control Panel → Network and Internet → Change adapter settings → right-click connection → Properties → select IPv4 → Use the following DNS addresses.
  
• macOS: System Settings → Network → select your active connection → DNS tab → add new servers.

After saving, test a few sites.

5. Temporarily disable IPv6

If your network supports IPv6 but your router or ISP doesn’t handle it properly, DNS lookups can hang. Disabling IPv6 is a quick diagnostic step:

• On Windows: Network and Sharing Center → Change adapter settings → right-click connection → Properties → uncheck Internet Protocol Version 6 (TCP/IPv6).
  
• On macOS: System Settings → Network → select your active interface → Details → uncheck IPv6 (if available).

If disabling IPv6 fixes the issue, you can keep it off or check your router’s IPv6 configuration.

6. Update network drivers or router firmware

Outdated or buggy drivers can cause connectivity issues, including DNS timeouts.

• On Windows, update your network adapter driver through Device Manager.
• On macOS and Linux, OS updates include network driver updates automatically.
• For routers, log in to the admin interface and check for firmware updates.

Once updates are applied, reboot everything and retest your connection.

These beginner steps often resolve the error without diving into advanced settings. If you’re still stuck, the next section covers deeper diagnostics and configuration fixes.

Advanced troubleshooting (for power users & IT pros)

If the quick fixes didn’t solve the problem, it’s time to go deeper.

The steps in this section use command-line tools and diagnostic utilities to uncover exactly where DNS resolution is failing. They’re aimed at users comfortable working with network settings or supporting systems at scale.

1. Use diagnostic tools (nslookup, dig, traceroute, ping)

Start by verifying how your system resolves DNS queries. Tools like nslookup (Windows, macOS, Linux) and dig (macOS, Linux) let you query DNS servers directly and see what responses you get.

Example:

nslookup uptimerobot.com

This shows which DNS server replied and what IP address it returned. If the request times out, specify another server to compare:

nslookup uptimerobot.com 8.8.8.8

Use dig for more detailed output:

dig uptimerobot.com

Focus on the ANSWER SECTION and Query time. If you get SERVFAIL or NXDOMAIN, the problem lies with your resolver or upstream server.

To test basic connectivity, run:

ping 8.8.8.8

If ping fails, the issue is likely network-related, not DNS.
You can also trace the route to a DNS server:

traceroute 8.8.8.8 # macOS/Linux

tracert 8.8.8.8 # Windows

Dropped packets or high latency suggest a routing or firewall issue rather than a DNS one.

Tip: For continuous monitoring, you can use website monitoring tools. They’ll keep you up to speed the moment something goes wrong.

2. Check DNS over HTTPS (DoH) settings

Modern browsers like Chrome and Firefox can encrypt DNS traffic using DNS over HTTPS (DoH). If the configured DoH provider is unreachable, your browser might show DNS errors even though system DNS still works.

• Chrome: Settings → Privacy and security → Security → Advanced → Use secure DNS
  
• Firefox: Settings → General → Network Settings → Enable DNS over HTTPS

Try disabling secure DNS temporarily. If pages start loading, the DoH resolver was likely the issue.

3. Inspect and reset the hosts file

Your hosts file overrides DNS lookups locally. Corrupted or modified entries can redirect or block domains.

Open the file with admin privileges and review it for strange or duplicate entries. Remove unauthorized lines or restore it to the default minimal version (just 127.0.0.1 localhost).

4. Router-level troubleshooting

If every device on your network shows the same error, the router may be at fault.

1. Log into your router’s admin panel (usually at 192.168.0.1 or 192.168.1.1).
   
2. Check WAN or Internet DNS settings and confirm they point to valid servers (e.g., 8.8.8.8 or 1.1.1.1).
   
3. Reboot the router or clear its DNS cache if the option exists.
   
4. Update to the latest firmware. Outdated builds can cause intermittent DNS failures.

For managed environments, verify that the router’s DHCP service isn’t distributing incorrect DNS information to connected devices.

5. Internal or enterprise DNS issues

In corporate or hybrid environments, DNS problems may originate from internal resolvers.

• Confirm that internal DNS servers are reachable (use ping or nslookup against them).
  
• Review split-horizon DNS configurations to ensure internal domains aren’t conflicting with public ones.
  
• Check DHCP options 6 and 15. Incorrect domain suffixes or DNS server IPs can cause failed lookups.
  
• On Linux servers, inspect /etc/resolv.conf and logs via journalctl -u systemd-resolved.
  
• On Windows Server, check the DNS Manager event logs for recursion or zone errors.

These diagnostic steps help narrow down whether the issue is local, network-wide, or upstream. Once you’ve isolated the source, you can apply targeted fixes without guesswork.

Fixing DNS issues on different devices

DNS errors can look different depending on the device you’re using, but the root cause is usually the same: your device can’t reach the DNS server that translates domain names into IP addresses.

Here’s how to troubleshoot DNS problems on major platforms.

Windows

On Windows, errors often appear as “DNS server isn’t responding” or “This site can’t be reached.”

Try the following:

Flush the DNS cache:

 ipconfig /flushdns

Restart the DNS client service:

net stop dnscache

net start dnscache

Switch to a public DNS:

• Control Panel → Network and Internet → Network and Sharing Center
  
• Change adapter settings → right-click connection → Properties
  
• Select Internet Protocol Version 4 (TCP/IPv4) → Properties
  
• Choose “Use the following DNS server addresses” and enter 8.8.8.8 and 8.8.4.4 (Google) or 1.1.1.1 (Cloudflare).

If that doesn’t help, check your firewall settings to ensure DNS queries over port 53 aren’t blocked.

macOS

Clear the DNS cache:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Change DNS servers:

• System Settings → Network → select active connection → Details
  
• Under DNS, add new servers like 1.1.1.1 and 8.8.8.8, then click OK → Apply.

Reset network interface (if needed):

Turn Wi-Fi off and on, or delete and re-add the network under Known Networks.

Linux (systemd-resolved)

Flush DNS cache:

sudo systemd-resolve --flush-caches

Check current DNS servers:

systemd-resolve --status

Edit resolv.conf or configure NetworkManager:

• /etc/resolv.conf may be symbolic-linked to systemd-resolved.
  
• Add public DNS servers if your ISP’s resolvers are slow or failing.

Check logs with journalctl -u systemd-resolved to see if your resolver is failing or timing out.

iOS

1. Go to Settings → Wi-Fi.
2. Tap the i next to your connected network.
3. Scroll to Configure DNS → switch to Manual.
4. Add servers such as 1.1.1.1 and 8.8.8.8.

For cellular data, you’ll need a VPN or DNS app (like Cloudflare’s 1.1.1.1 app) to override default DNS settings.

Android

Steps vary slightly by device and version:

1. Open Settings → Network & Internet → Internet.
2. Long-press your Wi-Fi network → Modify network.
3. Under IP settings, switch from DHCP to Static.
4. Enter DNS1 = 1.1.1.1, DNS2 = 8.8.8.8.

For mobile data, use a VPN or custom DNS app to override carrier DNS.

Routers and access points

If DNS issues affect every device on your network, start here:

1. Log into your router’s admin panel (usually 192.168.0.1 or 192.168.1.1).
2. Locate DNS settings under WAN or Internet.
3. Replace ISP-assigned DNS with public ones (Cloudflare, Google, or Quad9).
4. Save and reboot the router.

Some routers cache DNS lookups; if you’re still seeing errors, clear the cache (if supported) or restart the device.

Smart TVs, consoles, and streaming devices

These devices often have limited network settings but allow manual DNS configuration.

1. Open Network Settings → Manual setup.
2. Enter public DNS addresses.
3. Restart the device and test a connection.

These platform-specific fixes cover the most common ways DNS errors appear across hardware and operating systems.

If problems persist even after these steps, the issue likely lies with your router or DNS provider, not the device itself.

Choosing the best DNS server for speed & privacy

Not all DNS servers perform the same. Some are faster, some protect your privacy better, and some block malicious sites. Choosing the right one can make pages load quicker and keep your data secure.

Speed and reliability

The closer and better-maintained a DNS server is, the faster it responds.

Public DNS services like Google (8.8.8.8), Cloudflare (1.1.1.1), and Quad9 (9.9.9.9) run global networks with distributed data centers to reduce latency. Many use anycast routing, which automatically sends your query to the nearest node.

You can test resolution speed from your location using tools such as Namebench, DNSPerf, or GRC’s DNS Benchmark.

Privacy and data handling

DNS queries reveal which websites you visit. Some providers log this information, while others avoid it entirely.

Always review a provider’s privacy policy, especially if you’re configuring DNS for work or shared devices.

Testing and switching DNS servers

Before switching completely, test one device first to measure speed and reliability.

Example:

dig example.com @1.1.1.1

This queries Cloudflare directly and shows response time. Try the same command with other providers to compare.

Once you’ve chosen, update DNS settings on your system or router:

• Windows: Network & Internet Settings → Change Adapter Options → IPv4 → Use the following DNS server addresses
• macOS: System Settings → Network → DNS tab → Add servers
• Routers: Admin panel → WAN or DHCP options → Update DNS settings

Keep a note of your old settings in case you need to revert.

Choosing a DNS provider is rarely one-size-fits-all. Benchmark a few options, check their privacy policies, and pick the one that balances speed, uptime, and data protection for your needs.

Preventing DNS issues in the future

Once your DNS is working again, a few proactive steps can help you avoid future outages or slowdowns.

1. Use reliable and redundant DNS providers

Even the best DNS services experience downtime occasionally. Configure two or more providers (for example, Cloudflare + Google or Quad9) so your system has a fallback if one fails. If you manage your own DNS, distribute your authoritative nameservers across multiple regions and networks to prevent single points of failure.

2. Monitor DNS health

DNS problems often go unnoticed until users start complaining. Continuous monitoring alerts you to failures before they escalate.

Tools like UptimeRobot DNS Monitoring check whether your domain resolves correctly and send instant alerts for timeouts or missing records.

Downtime happens. Get notified!

Join the world's leading uptime monitoring service with 2.1M+ happy users.

Register for FREE

Tip: Monitor both public and internal DNS endpoints to catch regional or configuration-specific issues early.

3. Keep DNS configurations up to date

Expired domains, outdated records, or stale caches can all cause errors.

Regularly review and clean up your DNS records to remove unused entries and confirm that all A, AAAA, CNAME, and MX records point to the right destinations.

Set reminders to:

• Check domain and SSL certificate expiration dates
• Audit DNSSEC settings
• Update TTL values based on how often your records change

4. Strengthen security and reliability

• Enable DNSSEC to protect against tampering
• Use DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT) for encrypted lookups
• Run malware scans occasionally to prevent host file modifications
• Keep routers and firmware updated to reduce DNS hijacking risks

Taking a few preventive steps now can save hours of troubleshooting later. Combine redundancy, monitoring, and security best practices to keep your DNS, and your sites, stable and responsive.

Conclusion

DNS errors can be frustrating, but most are easy to diagnose once you know where to look. Restarting your router, flushing DNS cache, or switching to a public resolver fixes the majority of cases. For persistent or large-scale issues, tools like dig, nslookup, and active DNS monitoring help uncover deeper problems.

If you manage multiple sites or rely on uptime for business, automated DNS monitoring is the best safety net.

UptimeRobot’s DNS Monitoring continuously checks whether your domains resolve correctly and alerts you instantly when DNS records fail, change, or propagate incorrectly, so you can act before customers notice.

Keep your DNS healthy, responsive, and reliable. Monitor it automatically with UptimeRobot.