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 names like example.com into IP addresses like 203.0.113.10. Without a working DNS server, your browser can't find any website, even though your internet connection itself may be fine.

On Windows, Network Diagnostics reports it as "Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding." Chrome shows DNS_PROBE_FINISHED_BAD_CONFIG (your DNS server failed while Google's answered) or DNS_PROBE_FINISHED_NO_INTERNET (neither answered), both DNS_PROBE codes, Safari "Safari Can't Find the Server", and Firefox "Hmm. We're having trouble finding that site."

It doesn't always mean your internet is down. Often only the DNS step is broken, and you can fix that yourself in a few 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 usual reasons this error appears.

• 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
• Stale DNS cache — An old or failed entry your device cached; it breaks only the sites it covers, so it explains one site failing, not all of them

Fix 1: Flush Your DNS Cache

This takes ten seconds. Your system stores recent DNS answers in a cache, and flushing it clears any stored failure so the next lookup goes out fresh. (A stale entry affects only its own site; if nothing loads, also do Fixes 2 and 3.) See how to flush DNS for every system.

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

# Windows (Command Prompt)
ipconfig /flushdns

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

# Linux (systemd-resolved)
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. The DNS settings path below is Windows 11's; Windows 10 is covered right after it.

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 → Wi-Fi → Manage known networks → your network (for a cable: Ethernet → your network)
• Click Edit next to DNS server assignment
• Switch from Automatic to Manual and turn on IPv4
• Enter Preferred DNS 1.1.1.1 and Alternate DNS 1.0.0.1. If there's an IPv6 section, also enter 2606:4700:4700::1111 and 2606:4700:4700::1001, or the device keeps asking your provider's IPv6 DNS.
• Click Save and test by visiting a website

Windows 10 has no separate DNS option in Settings: press Win + R, run ncpa.cpl, right-click your adapter → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → Use the following DNS server addresses.

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 (and 2606:4700:4700::1111 if you use IPv6)
• Click OK

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

en0 is usually Wi-Fi on a MacBook; find yours with networksetup -listallhardwareports.

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 (plus 2606:4700:4700::1111 and 2606:4700:4700::1001 for IPv6)
• 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 (under Advanced on some phones; on Samsung, Connections → More connection settings)
• Select Private DNS provider hostname
• Enter one.one.one.one (Cloudflare) or dns.google (Google), exactly as written
• Tap Save — it applies on Wi-Fi and mobile data. A typo here breaks every lookup on the phone, and Android warns "Private DNS server cannot be accessed"

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 a PlayStation:

• PS5: Settings → Network → Settings → Set Up Internet Connection, highlight your network, press Options → Advanced Settings → DNS Settings: Manual
• PS4: Settings → Network → Set Up Internet Connection → Use Wi-Fi (or Use a LAN Cable) → Custom, keep the IP and DHCP defaults, then DNS Settings: Manual
• Enter Primary DNS 1.1.1.1 and Secondary DNS 1.0.0.1
• Save, then 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. Temporarily disable your firewall and antivirus to test.

If the error disappears with the firewall off, add an exception for DNS traffic (port 53, UDP and TCP; for Android Private DNS, TCP 853, or UDP 443 when it points at Google's or Cloudflare's DNS, which Android 11 and later reach over DNS over HTTP/3 (Google)) in your security software settings. Do not leave your firewall permanently disabled.

Disable IPv6

If IPv6 on your network is half-working, DNS over IPv6 can fail while IPv4 works. Turning IPv6 off on the device is a quick test; if it helps, fix the router's IPv6 or set IPv6 DNS servers rather than leaving it off (Microsoft recommends against disabling IPv6 on Windows):

• 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. Don't just open a website: run these tests to confirm DNS answers again.

# 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
scutil --dns | head -20      # macOS
resolvectl status            # Linux with systemd-resolved

If nslookup returns an IP address, DNS is working. To compare with what DNS says elsewhere, look the domain up with DNS Lookup or the DNS Propagation Checker.