How to Fix DNS Server Not Responding (Step-by-Step)

What Does DNS Server Not Responding Mean?

DNS Server Not Responding is an error that appears when your device sends a request to a DNS server and gets no reply. DNS (Domain Name System) translates human-readable domain names like example.com into IP addresses like 93.184.216.34. Without a working DNS server, your browser cannot find any website — even though your internet connection may be perfectly fine.

You will typically see this error as "DNS server isn't responding" in Windows Network Diagnostics, or as DNS_PROBE_FINISHED_NO_INTERNET in Chrome. Safari shows "Safari Can't Find the Server" and Firefox displays "Hmm. We're having trouble finding that site."

The good news: this error almost never means your internet is truly down. It means the DNS layer is broken, and that is something you can fix yourself in under 5 minutes.

Common Causes of DNS Server Not Responding

Before jumping to fixes, understanding the root cause helps you pick the right solution. Here are the most common reasons this error appears.

• Stale DNS cache — Your device cached an old or corrupted DNS entry that is now invalid

• ISP DNS server is down — Your internet provider's DNS servers are overloaded or experiencing an outage

• Router glitch — A firmware bug or memory leak in your router is blocking DNS traffic

• Firewall or antivirus blocking DNS — Security software is interfering with DNS requests on port 53

• Wrong DNS settings — Manual DNS configuration with incorrect or unreachable server addresses

• Network adapter issue — Outdated driver or corrupted TCP/IP stack on your device

• WiFi connectivity problem — Weak signal or intermittent disconnects causing DNS timeouts

• VPN interference — Active VPN tunneling DNS queries through an unresponsive server

Fix 1: Flush Your DNS Cache

This is the most common fix and takes 10 seconds. Your operating system stores DNS lookups in a local cache. If an entry becomes stale or corrupted, all DNS lookups can fail. Flushing the cache forces your device to query DNS servers fresh.

Open a terminal or command prompt and run the command for your operating system:

# Windows (Command Prompt as Administrator)
ipconfig /flushdns

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux
sudo systemd-resolve --flush-caches
# or
sudo resolvectl flush-caches

Fix 2: Switch to a Public DNS Server

If your ISP's DNS servers are slow or down, switching to a reliable public DNS resolver often fixes the problem instantly. Public DNS servers like Google and Cloudflare have global infrastructure with near-perfect uptime.

Here are the best free DNS servers to use:

Fix 3: Restart Your Router and Device

A simple power cycle clears temporary glitches in your router's memory and forces it to re-establish DNS connections. This is especially effective when the DNS error affects every device on your network.

Follow these steps in order:

• Unplug your router from power (not just turn off — physically unplug it)

• Wait 30 seconds — this clears the router's RAM and resets all temporary state

• Plug it back in and wait 1-2 minutes for it to fully boot and reconnect to your ISP

• Restart your computer or phone to clear any device-level network state

• Test by visiting a website in your browser

Fix DNS Server Not Responding on Windows

If the three quick fixes above did not work, follow these Windows-specific steps. These cover Windows 10 and Windows 11.

Reset Your Network Adapter

Open Command Prompt as Administrator and run these commands to fully reset your network stack:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Restart your computer after running these commands. This resets the Winsock catalog, TCP/IP stack, releases and renews your IP address, and flushes the DNS cache in one sequence.

Change DNS Settings on Windows

To manually set a public DNS server on Windows:

• Open Settings → Network & Internet → Advanced network settings

• Click your active connection (Wi-Fi or Ethernet) → Hardware properties

• Click Edit next to DNS server assignment

• Switch from Automatic to Manual and enable IPv4

• Enter Preferred DNS: 1.1.1.1 and Alternate DNS: 1.0.0.1

• Click Save and test by visiting a website

Fix DNS Server Not Responding on Mac

macOS uses a different DNS management system. Here is how to fix it.

Change DNS Settings on macOS

To set a public DNS server on your Mac:

• Open System Settings → Network → Wi-Fi (or your active connection)

• Click Details next to your connected network

• Click DNS in the sidebar

• Click the + button and add 1.1.1.1

• Click + again and add 1.0.0.1

• Click OK and then Apply

Flush DNS and Reset Network on Mac

Open Terminal and run:

# Flush DNS cache
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

# Renew DHCP lease (forces new DNS assignment)
sudo ipconfig set en0 DHCP

Replace en0 with en1 if you are using a USB Ethernet adapter. You can check your interface name with ifconfig in Terminal.

Fix DNS Server Not Responding on Mobile

DNS errors on phones and tablets are usually caused by your WiFi router's DNS settings or a stale cache on the device.

iPhone / iPad (iOS)

To change DNS on iOS:

• Open Settings → Wi-Fi → tap the (i) icon next to your connected network

• Tap Configure DNS → switch from Automatic to Manual

• Delete existing DNS servers and add 1.1.1.1 and 1.0.0.1

• Tap Save and test your connection

Android

Android 9+ has a built-in Private DNS setting that applies to all networks:

• Open Settings → Network & Internet → Private DNS

• Select Private DNS provider hostname

• Enter: one.dot.one.dot.one.dot.one (for Cloudflare) or dns.google (for Google)

• Tap Save — this applies across all Wi-Fi and cellular connections

Fix DNS Server Not Responding on Gaming Consoles

DNS errors on gaming consoles prevent online multiplayer, game updates, and store access. Here is how to fix it on PlayStation and Xbox.

PlayStation (PS5 / PS4)

To change DNS on your PlayStation:

• Go to Settings → Network → Settings → Set Up Internet Connection

• Select your connection (Wi-Fi or LAN) and choose Custom

• Keep defaults for IP Address (Automatic) and DHCP Host Name (Do Not Specify)

• For DNS Settings select Manual

• Enter Primary DNS: 1.1.1.1 and Secondary DNS: 1.0.0.1

• Keep remaining settings as default and test the connection

Xbox (Series X/S / One)

To change DNS on Xbox:

• Go to Settings → General → Network settings → Advanced settings

• Select DNS settings → Manual

• Enter Primary DNS: 1.1.1.1 and Secondary DNS: 1.0.0.1

• Press B to save and restart the console to apply changes

Advanced Troubleshooting

If none of the above fixes worked, the problem may be deeper. Try these advanced steps.

Disable Firewall or Antivirus Temporarily

Some security software blocks DNS traffic on port 53. Temporarily disable your firewall and antivirus to test:

If the error disappears with the firewall off, add an exception for DNS traffic (UDP port 53) in your security software settings. Do not leave your firewall permanently disabled.

Disable IPv6

IPv6 DNS resolution can sometimes conflict with your network configuration. Temporarily disabling it forces your device to use IPv4 DNS only:

• Windows: Open Network adapter properties → uncheck "Internet Protocol Version 6 (TCP/IPv6)" → click OK

• Mac: System Settings → Network → Wi-Fi → Details → TCP/IP → set Configure IPv6 to "Link-Local Only"

• Linux: Run sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1

Boot in Safe Mode with Networking

Safe mode loads Windows with minimal drivers and services, eliminating interference from third-party software. If DNS works in safe mode, a startup program or driver is causing the conflict.

On Windows: hold Shift while clicking Restart, then choose Troubleshoot → Advanced Options → Startup Settings → Restart → press F5 for Safe Mode with Networking.

How to Verify DNS Is Working Again

After applying a fix, verify that DNS resolution is working properly. Do not just open a website — run these tests to confirm the fix is permanent.

# Test DNS resolution directly
nslookup google.com

# Test with a specific DNS server
nslookup google.com 1.1.1.1

# Check your current DNS settings (Windows)
ipconfig /all | findstr "DNS"

# Check your current DNS settings (Mac/Linux)
cat /etc/resolv.conf

If nslookup returns an IP address, DNS is working. You can also use DNS Robot's free DNS Lookup tool to test DNS resolution from multiple global servers simultaneously — this confirms the issue is resolved everywhere, not just on your device.