How to the Fix “DNS Server Not Responding” Error – Detailed Guide

Key Takeaways

• The “DNS Server Not Responding” error stops browsing due to failed DNS lookups.
• Restarting your router can resolve temporary DNS issues quickly.
• Changing to a reliable DNS server like Google or Cloudflare can improve connection stability.
• Regularly checking DNS records and using reliable providers reduces recurring DNS issues.

DNS issues interrupt the connection at the earliest stage. A page may stop loading, a login may fail, or a device may lose access after switching networks. Each scenario leads to the same result: the browser reports DNS Server Not Responding because the DNS lookup cannot return an IP address.

DNS has a single job: it matches a domain name to the server that hosts it. The lookup must succeed before any request can move forward. When any point in that path fails, the browser stops at the DNS step and ends the connection.

The DNS Server Not Responding error often appears during routine browsing. Teams see it while testing deployments, adjusting DNS settings, or switching networks. The pattern looks different in each case, but the underlying cause is always the same: the device cannot complete the lookup.

This guide explains why DNS lookups fail and shows how to fix DNS resolution issues step by step. Every major scenario is covered so the source becomes easier to pinpoint.

First, let’s learn what this common WordPress error actually means.

What the DNS Server Not Responding Error Means

The error appears when a device sends a DNS request but receives no valid response. The lookup begins, the resolver stays inactive, and the browser stops because it cannot continue without an IP address.

A DNS server stores the records that link domain names to their destinations. The device contacts that server first and waits for an answer. When the server cannot be reached or responds in an unusable way, the resolution step fails and the connection ends at that point.

Different conditions can block this exchange. Some prevent the request from leaving the device. Others interrupt the reply before it returns. The results look the same on the screen, which is why the message appears across many scenarios.

Some quick checks can rule out simple issues before moving into deeper fixes, so let’s look at those first.

Quick Checks to Fix the “DNS Server Not Responding” Error Fast

These checks confirm whether the DNS Server Not Responding issue originates from the device, the network, or the DNS server. Each step removes a possible failure point and and guides your DNS troubleshooting for the next step.

#1 Test Your Internet Connection

Open a site that does not rely on cached data. A loading delay or a complete stall suggests a broader network issue. The DNS Server Not Responding error may appear because the device cannot reach any external service.

If the site opens, the connection is active and the problem is likely limited to DNS resolution.

#2 Try a Different Browser

Switch to another browser and load the same domain. A successful load indicates the first browser blocked or failed the DNS request. If multiple browsers fail, the DNS Server Not Responding issue is likely at the network or DNS layer.

#3 Test Another Device on the Same Network

Check the same site on a second device connected to the same WiFi or wired network. If both fail, the issue is likely in the router or upstream DNS service. If only one device fails, the problem lies within that device’s DNS configuration.

#4 Try Mobile Data to Rule Out Local Network Issues

Open the site on a phone using mobile data. A successful load here shows the external site is reachable. The earlier failure then likely comes from the local network or the router’s DNS configuration.

If the site fails on mobile data as well, the target domain may have its own DNS or hosting issue.

Prevent DNS Resolution Errors with Cloudways WordPress Hosting

Cloudways managed WordPress hosting provides reliable DNS integration, stable server environments, and managed infrastructure to help prevent DNS related issues.

TRY NOW

How to Fix the “DNS Server Not Responding” Error (9 Easy Fixes)

Devices stop the request when something interrupts the DNS lookup. Working through the fixes below helps reveal where the interruption occurs and restores normal resolution.

1. Restart Your Router and Modem

Routers sometimes drop DNS requests or return outdated routing data. Restarting clears temporary faults.

Steps:

• Turn off the router and modem.
• Wait 10 to 15 seconds.
• Turn them back on.
• Try loading the site again.

2. Run Network Troubleshooter (Windows or macOS)

The built-in troubleshooting tools check for blocked DNS requests and highlight local network faults. Running these tests helps confirm whether the issue sits inside the device rather than on the network or DNS server.

Steps (Windows 11):

• Open Settings.
• Go to System → Troubleshoot → Other troubleshooters.
• Find Internet Connections.
• Click Run to start the troubleshooter.

Steps (macOS):

• Hold Option and click the Wi-Fi icon in the menu bar.
• Select Open Wireless Diagnostics and follow the on-screen steps.

Optional: For additional checks, go to System Settings → Network → Wi-Fi → Details → TCP/IP and click Renew DHCP Lease to refresh your connection.

3. Disable Extra Network Connections

VPN tools, virtual adapters, and unused interfaces can reroute or block DNS packets. Disabling non-essential connections ensures that DNS requests leave through the correct interface.

Steps (Windows):

• Open Network Connections.
• Disable unused adapters such as virtual machine interfaces, old Ethernet ports, or inactive VPN adapters.
• Keep only the active WiFi or Ethernet interface enabled.
• Test the site again.

Steps (macOS):

• Open System Settings → Network.
• Review all listed interfaces (Wi-Fi, Ethernet, VPN, etc.).
• Disable or remove unused VPN profiles, virtual adapters, or inactive interfaces.
• Confirm that your active connection (Wi-Fi or Ethernet) is at the top of the service order.

4. Flush DNS Cache and Renew IP

Stale DNS entries or outdated routing data can block new lookups. Clearing the DNS cache and renewing your IP forces the device to request fresh records and rebuild its routing information.

Steps (Windows):

• Open Command Prompt.
• Run:

 ipconfig /flushdns

• Then renew your IP address:

ipconfig /renew

Steps (macOS):

• Open Terminal.
• Run the command for macOS Big Sur or later:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

• Note: This command produces no output when it succeeds. This is normal.

5. Change Your DNS Server

If the current resolver is slow or offline, switching to a public DNS service restores the lookup.

Steps (Windows 11):

• Open Settings.
• Go to Network & Internet.
• Select Wi-Fi (or Ethernet, if using a wired connection).
• Click your active network name.
  (Example: MyHomeNetwork, OfficeWiFi, etc.)
• Scroll to DNS server assignment and click Edit.

• Change the dropdown to Manual.
• Turn IPv4 ON.

• Enter your preferred DNS servers:
  • Google DNS: 8.8.8.8
  • Alternate: 8.8.4.4
    or
  • Cloudflare DNS: 1.1.1.1
  • Alternate: 1.0.0.1
• Save the changes and retry loading the website.

Steps (macOS):

• Open System Settings.
• Go to Network.
• Select Wi-Fi (or Ethernet).

• Click the Details button.
• Open the DNS tab.

• Add your DNS servers using the + button.
• Save the changes.

6. Disable IPv6 Temporarily

Some routers and ISPs do not handle IPv6 lookups correctly. Disabling IPv6 forces the device to rely on IPv4-only resolution, which often removes conflicts caused by partial or unstable IPv6 support. (Check our guide on IPv4 vs IPv6)

Steps (Windows 11):

• Open Settings.
• Go to Network & Internet.
• Select Wi-Fi (or Ethernet, if using a wired connection).
• Click your active network name.
• Scroll down and click Edit under IP assignment.
• Select Manual.
• Turn IPv6 OFF (or ensure only IPv4 is enabled).
• Save the changes and try loading the site again.

Steps (macOS):

Some macOS versions allow adjusting IPv6 behavior through the interface settings.

• Open System Settings → Network.
• Select your active interface (Wi-Fi or Ethernet).
• Click Details → TCP/IP.
• If available, change Configure IPv6 to Link-local only.
• Apply the changes and test the connection.

Note: Certain macOS versions do not allow fully disabling IPv6 directly. If the option is unavailable, you can still test IPv6 behavior by switching DNS servers or rebooting the connection.

7. Update or Reinstall Network Drivers

Outdated or corrupted network drivers can drop DNS packets before they reach the router. Updating or reinstalling the driver restores proper communication between the device and the network.

Steps (Windows 11):

• Press Windows + X and select Device Manager.
• Expand Network adapters.
• Right-click your active Wi-Fi or Ethernet adapter.
• Choose Update driver and select “Search automatically for drivers.”
• If the adapter is malfunctioning, select Uninstall device and restart your computer to reinstall it automatically.

Steps (macOS):

macOS updates network drivers through system updates rather than manual installation.

• Open System Settings → General → Software Update.
• Install any pending macOS updates, which include networking fixes and driver updates.
• Restart your device and test the connection again.

8. Boot in Safe Mode

Safe Mode loads only essential components. If DNS resolution works here, a background service, app, or security tool is likely interrupting the lookup.

Steps (Windows):

• Open the Start menu.
• Hold Shift and select Restart.
• Choose Troubleshoot → Advanced options → Startup Settings.
• Select Safe Mode with Networking.
• Try loading the site again.

Steps (macOS):

• Turn off your device.
• Turn it back on while holding the Shift key.
• Log in to complete the Safe Mode boot.
• Test your DNS resolution while in this environment.

If the site loads in Safe Mode, a third-party app, extension, or background service is likely blocking DNS traffic during normal operation.

9. Temporarily Disable Antivirus or Firewall

Security tools sometimes block or redirect DNS traffic. Disabling them briefly helps confirm whether they are filtering or interrupting the lookup.

Steps (Windows):

• Turn off your third-party antivirus or firewall software temporarily.
• If needed, open Windows Security → Firewall & network protection and turn off the active profile’s firewall.
• Test the DNS request.
• Turn protection back on immediately after testing.

Steps (macOS):

• Open System Settings → Network → Firewall.
• Temporarily disable the firewall.
• If you use third-party security tools, pause their protection as well.
• Try loading the site again.
• Re-enable the firewall or security tool right after testing.

Fixing “DNS Server Not Responding” When It Happens in Specific Situations

Some DNS issues do not appear in every context. They surface only under specific conditions, which reveals patterns the general fixes cannot catch. These scenarios point toward more targeted causes, and each one has a clear way forward.

1. The Error Appears Only on WiFi

A WiFi network can interrupt DNS requests through weak signals or unstable channels. Switching to Ethernet helps confirm whether the wireless path is the source. If Ethernet works, adjust the WiFi channel or reconnect to the network to restore stable resolution.

2. The Error Appears Only on One Website

A single website failure often points to a domain-side DNS issue rather than a device or router fault. Testing the same domain on another device or mobile data helps confirm this. If every test fails, the domain’s DNS records or hosting setup are likely misconfigured.

3. The Error Appears After Sleep or Hibernate

Some devices lose their DNS routes after waking from low-power states. Resetting power settings for the network adapter helps keep DNS requests intact. Reconnecting to the network also refreshes the route when the adapter does not resume properly.

4. Older Adapters Fail on New Routers

Compatibility issues can surface when older WiFi adapters communicate with modern dual-band routers. Switching to the 2.4 GHz network provides a more stable handshake. Updating the adapter driver strengthens support for both frequencies.

5. Security Suites or VPNs Break DNS Requests

Security tools sometimes redirect or filter DNS traffic. Disabling them briefly helps verify whether they are blocking the lookup. If the site loads with the tool off, adjust the DNS or routing rules inside the software before turning it back on.

The scenarios above focus on issues that appear only on specific devices or networks. When visitors encounter the error while loading your website, the cause often shifts to the DNS or hosting layer. The next section explains those cases.

Why Your Website Shows a “DNS Server Not Responding” Error (Hosting and DNS Side Issues)

The error can also appear for users trying to reach a specific website. In these cases, the problem is not on the visitor’s device. It usually comes from issues in the domain’s DNS configuration or the hosting environment that serves the site.

1. Incorrect Nameservers or DNS Records

A domain depends on nameservers to point users to the correct DNS host. If the nameserver entries are wrong, outdated, or incomplete, the resolver cannot return the right IP address. The lookup stops, and visitors see the DNS Server Not Responding message.

DNS records can create the same outcome. A missing A record, an incorrect IPv6 entry, or a misrouted CNAME causes the resolver to return no usable data.

2. Slow DNS Propagation or High TTL Values

DNS changes take time to reach resolvers across the internet. A high TTL value extends that delay. During this period, users may continue hitting outdated records that no longer point to a valid server.

Propagation delays often appear after switching hosting, adjusting nameservers, or moving domains between providers.

3. DNS Provider Outages or Misconfigurations

DNS providers can experience downtime, network congestion, or routing faults. When this happens, requests may never reach the DNS servers that hold the domain’s records. Visitors then see DNS-related errors even if the hosting server itself is healthy.

Large traffic spikes or partial outages can trigger the same response.

4. Attacks That Target DNS Resolution

Some attacks overload or poison DNS routes. A DNS DDoS attack can overwhelm the resolver and prevent it from returning responses. Poisoned caches can send users toward invalid or unsafe routes, causing the lookup to break.

Websites that rely on a single DNS provider or lack DNS protection are more vulnerable to these failures.

5. Tools to Diagnose DNS and Hosting Issues

A few checks can confirm whether the issue originates from the website’s DNS setup. Tools like dig, nslookup, and online DNS checkers show whether the domain resolves correctly across global resolvers. Traceroute helps identify where the request stalls on its way to the DNS server or hosting environment.

These tools point directly to the layer that requires attention, reducing time spent guessing.

DNS issues at the website level affect anyone trying to reach the domain. Preventing these problems requires stable records, reliable resolvers, and predictable routing behavior. The next section outlines ways to keep DNS resolution consistent over time.

How to Prevent the “DNS Server Not Responding” Error Permanently

Preventing DNS issues depends on keeping the resolution path stable. Small adjustments in network settings, DNS records, or provider choices can stop these failures from appearing again.

1. Use Reliable DNS Providers

Some providers return responses faster and with fewer interruptions. Services like Cloudflare DNS and Google DNS maintain global networks that handle high load and regional spikes. Using a dependable resolver reduces the chance of failed lookups.

2. Keep Network Drivers and Operating Systems Updated

Updates include fixes for DNS routing, adapter stability, and network protocols. Keeping devices current helps avoid drops in the resolution stage.

3. Review DNS Records and TTL Values Regularly

DNS records can become outdated after site migrations, platform changes, or server adjustments. Reviewing A, AAAA, and CNAME records ensures they still point to active servers. Lower TTL values allow corrections to propagate faster when changes are needed.

4. Enable Domain Locks and DNSSEC

DNSSEC adds validation to DNS responses, which protects visitors from cache poisoning. Registrar locks prevent unauthorized changes to nameservers or DNS settings. Both create a more predictable domain state and reduce resolution failures.

Strong DNS practices reduce the chances of unexpected resolution failures. Hosting platforms with stable routing and integrated DNS tools can extend that reliability further. The next section looks at how managed environments support this.

How Cloudways Helps Reduce DNS-Related Downtime

Managed environments can prevent many DNS issues before they reach users. Cloudways supports this by stabilizing routing paths, handling DNS changes cleanly, and reducing common failure points in the hosting layer.

1. DNS Integration Options for Consistent Resolution

Cloudways does not provide an in-house managed DNS service, but it supports DNS configuration through your domain registrar or through integrated add-ons.

You can manage your domain’s DNS records externally (A, AAAA, and CNAME) and point them to your Cloudways server’s IP address. For users who want advanced DNS performance and uptime features, Cloudways offers the DNS Made Easy add-on, which provides enterprise-level DNS management from within the Cloudways platform.

2. Cloudflare Enterprise for Faster Global Lookups

Cloudways users can enable Cloudflare Enterprise to improve DNS performance. The network resolves queries from locations close to the visitor and absorbs spikes that could cause resolver delays. This setup helps prevent DNS timeouts during load or regional congestion.

3. Built-In Monitoring for Early Detection

Cloudways includes monitoring tools that track server response, application availability, network routes. Alerts highlight irregular behavior early so DNS-related issues can be corrected before they reach users.

The hosting layer solves many upstream issues, but individual devices can still run into local faults. Questions about the DNS Server Not Responding message come up frequently, and the next section addresses the ones that appear most often.

Experience Fewer Hosting Errors with Cloudways Autonomous

Autonomous uses Kubernetes-based autoscaling and managed infrastructure to reduce configuration issues, handle traffic spikes automatically, and keep your site stable and responsive.

Try Today

Final Thoughts

DNS failures stop the connection before it has a chance to begin, which is why the browser reports the DNS Server Not Responding error so quickly. The lookup may fail on the device, inside the network, or at the DNS or hosting layer, but each case traces back to the same point: the resolver cannot return a usable IP address. This is a common form of DNS resolution issue that can affect browsing, application logins, and website access.

Working through the checks and fixes in this guide helps narrow down where that interruption occurs. Quick tests rule out simple issues, deeper fixes address network or DNS configuration faults, and the scenario-based sections highlight patterns that reveal more specific causes. Effective DNS troubleshooting ensures that your DNS records, resolvers, and routing behavior are all functioning correctly.

With stable DNS records, reliable resolvers, and consistent routing behavior, the DNS Server Not Responding error becomes far less likely to appear. Even when it does occur, understanding how the lookup works and following proper DNS troubleshooting techniques makes the source easier to pinpoint and resolve.