How to Fix DNS Server Not Responding on a Home Network (2026 Guide)

You are connected to your WiFi. Your signal bars are full. Yet every website you try to visit shows that dreaded error: “DNS Server Not Responding.” If this sounds familiar, you are not alone. Our team has dealt with this exact problem on countless home networks, and the good news is that almost every case is fixable without calling your ISP.

This guide walks you through how to fix DNS server not responding on a home network using a proven, ordered approach. We start with the simplest solutions (the ones that work most of the time) and move toward more advanced fixes if the basic ones do not resolve it. Every step includes exact commands and clear instructions for Windows, Mac, and mobile devices.

Here is what we will cover:

• What the DNS error actually means and why it happens
• How to confirm DNS is the real problem before you start fixing
• Seven step-by-step fixes ordered from easiest to most advanced
• How to change DNS settings on Windows, Mac, iPhone, and Android
• Router-level DNS configuration for a permanent fix
• How to stop the error from coming back

Whether you are troubleshooting a single device or your entire home network is down, these steps will get you back online. Let us start with understanding what is actually happening behind that error message.

What Does DNS Server Not Responding Mean?

DNS stands for Domain Name System. Think of it as the phonebook of the internet. When you type a website name like “google.com” into your browser, DNS translates that human-friendly name into a machine-readable IP address that computers use to find each other on the network.

When you see a “DNS server not responding” error, it means your device sent a lookup request to a DNS server and never got an answer back. Your browser has no idea what IP address to connect to, so it gives up and displays the error. You still have an internet connection in many cases, but without DNS, that connection is useless for normal browsing.

This is different from a “no internet” error. With a DNS problem, your device is often still connected to your router and may even be able to ping raw IP addresses. The issue is specifically that the translation layer between names and numbers has broken down.

Home networks are particularly vulnerable to DNS issues because they rely on ISP-provided DNS servers that can be slow, overloaded, or temporarily down. When dozens of homes share the same ISP DNS resolver, a single outage can affect everyone on your block.

How to Test if DNS Is Actually the Problem

Before you start applying fixes, it helps to confirm that DNS is genuinely the culprit. Sometimes what looks like a DNS error is actually a broader connectivity issue, a misconfigured firewall, or even a browser glitch.

The fastest test is to try reaching a website by its raw IP address instead of its domain name. Open Command Prompt on Windows or Terminal on Mac, and type: ping 8.8.8.8. If you get replies, your internet connection is working and the problem is almost certainly DNS-related. If the ping fails or times out, you have a broader connectivity issue that goes beyond DNS.

You can also run the built-in Windows Network Diagnostics tool. Right-click the network icon in your system tray and select “Diagnose network problems.” Windows will run a series of tests and, if DNS is the issue, it will explicitly mention that the DNS server is not responding. This is a quick way to confirm the diagnosis before moving on to fixes.

If only one device on your network is affected while others browse fine, the problem is device-specific. If all devices show the same DNS error, the issue is at the router or ISP level.

Common Causes of DNS Server Not Responding

Understanding the root cause makes it much easier to pick the right fix. Here are the six most common reasons your DNS server is not responding, based on what users on forums like Reddit’s r/techsupport report most frequently.

1. Corrupted DNS cache. Your computer stores recent DNS lookups locally to speed up browsing. If that cache becomes corrupted with bad or outdated entries, it can cause lookup failures. Power outages, improper shutdowns, and software crashes are common triggers for cache corruption.

2. Router or modem issues. Your router acts as a middleman between your devices and your ISP’s DNS servers. If the router is overheating, running old firmware, or has been running for weeks without a restart, it can fail to forward DNS requests properly.

3. Outdated network adapter drivers. The network adapter in your computer needs software drivers to communicate with your router. Outdated or buggy drivers can cause all sorts of connectivity problems, including DNS failures. This is especially common after major Windows updates.

4. Firewall and antivirus interference. Security software inspects network traffic to protect you from threats. Sometimes it gets too aggressive and blocks legitimate DNS traffic on port 53. Multiple users on r/techsupport report that Avast antivirus in particular can silently block DNS, and disabling it temporarily resolves the issue immediately.

5. ISP DNS server outages. Your internet service provider runs DNS servers for all its customers. If those servers go down or become overloaded, every device using them will see DNS errors. This is entirely outside your control, but switching to a public DNS server bypasses the problem completely.

6. Router firmware problems. Router manufacturers release firmware updates to fix bugs and improve performance. If your router is running outdated firmware, it may have known DNS-handling bugs. Many users never update their router firmware, leaving these issues unpatched for years.

How to Fix DNS Server Not Responding: Step-by-Step

Work through these fixes in order. Each one targets a specific cause, and we explain why each fix works so you understand what you are actually doing. Most people find their solution within the first three steps.

Fix 1: Restart Your Router and Device

This is the single most effective DNS fix, and it works more often than any other solution. Forum users consistently confirm that restarting the router resolves DNS errors in the majority of cases.

Here is the right way to do it. Unplug your router and modem from power. Wait at least 30 seconds (60 is better) to allow capacitors to fully drain and the devices to clear their temporary memory. Plug the modem back in first, wait for it to fully connect, then plug in the router. Wait another two minutes for the router to establish its connection before testing your browser.

Why this works: restarting clears the router’s DNS cache, forces it to re-establish its connection with your ISP, and requests fresh DNS server assignments via DHCP. It also clears any temporary glitches that were preventing DNS requests from being forwarded.

Restart your computer or device at the same time. This clears your local DNS cache and forces your network adapter to start fresh.

Fix 2: Flush Your DNS Cache

If restarting did not help, the next step is to manually clear your device’s DNS cache. This removes any corrupted or outdated entries that might be causing lookups to fail.

On Windows (Windows 10 and Windows 11):

Open Command Prompt as Administrator. You can do this by searching “cmd” in the Start menu, right-clicking “Command Prompt,” and selecting “Run as administrator.”

Type the following commands, pressing Enter after each one:

ipconfig /flushdns

ipconfig /release

ipconfig /renew

The first command flushes your DNS resolver cache. The second releases your current IP address, and the third requests a new one from your router’s DHCP server. You should see a “Successfully flushed the DNS Resolver Cache” confirmation message.

On Mac:

Open Terminal (Applications > Utilities > Terminal). The command you use depends on your macOS version.

For macOS Ventura and later, type: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

For macOS Monterey and earlier, type: sudo dscacheutil -flushcache

You will need to enter your administrator password. Terminal will not show characters as you type the password, which is normal.

Why this works: flushing the cache forces your device to query the DNS server fresh for every website, bypassing any corrupted entries that were stored locally.

Fix 3: Change to a Public DNS Server

If flushing the cache did not work, your ISP’s DNS servers may be the problem. Switching to a public DNS server is one of the most reliable permanent fixes for recurring DNS errors. Public DNS servers are operated by companies like Google and Cloudflare, and they tend to be faster and more reliable than ISP-provided alternatives.

Here are the most popular public DNS options:

• Google DNS: 8.8.8.8 and 8.8.4.4 (widely trusted, fast, and reliable)
• Cloudflare DNS: 1.1.1.1 and 1.0.0.1 (focused on privacy and speed)
• OpenDNS: 208.67.222.222 and 208.67.220.220 (includes optional content filtering)

You can change DNS at the device level or the router level. Device-level changes are faster to test, while router-level changes apply to every device on your network at once. We cover both approaches later in this guide.

Why this works: public DNS servers are maintained by companies with massive infrastructure and redundancy. If one server goes down, another takes over instantly. They are almost never offline, which means your lookups will succeed where your ISP’s servers failed.

Multiple users on r/techsource recommend setting a static DNS like 8.8.8.8 as a permanent fix rather than repeatedly restarting the router. Once you switch, the DNS error typically does not return.

Fix 4: Reset Your Network Adapter and Renew Your IP

If changing DNS servers did not resolve the issue, your network adapter’s configuration may be corrupted. Windows has a built-in tool to reset all network components to their default state.

Open Command Prompt as Administrator and run these commands one at a time:

netsh winsock reset

netsh int ip reset

ipconfig /flushdns

ipconfig /release

ipconfig /renew

Restart your computer after running these commands. The winsock reset clears and rebuilds the Windows network stack, while the IP reset restores TCP/IP settings to factory defaults. This is a more thorough version of the cache flush from Fix 2.

Why this works: over time, network settings can accumulate conflicts from VPN software, virtual adapters, and system updates. Resetting wipes the slate clean so DNS requests can flow through without interference.

On Mac, you can achieve a similar reset by going to System Settings > Network, removing your WiFi connection, and re-adding it. This forces macOS to rebuild the network configuration from scratch.

Fix 5: Update Your Network Adapter Driver

An outdated or buggy network adapter driver can cause DNS failures, especially after a Windows update installs new system files that conflict with old drivers. This fix is Windows-specific.

Right-click the Start button and select “Device Manager.” Expand the “Network adapters” section. Find your WiFi or Ethernet adapter (it will have names like “Intel Wireless,” “Realtek PCIe,” or “Broadcom”).

Right-click your adapter and select “Update driver.” Choose “Search automatically for drivers.” If Windows finds an update, install it and restart your computer.

If Windows says your driver is already up to date, try visiting your computer manufacturer’s website (Dell, HP, Lenovo, etc.) and downloading the latest network driver manually. The automatic search sometimes misses newer versions.

Why this works: drivers handle the low-level communication between your operating system and your network hardware. A driver bug can silently drop DNS packets, and updating to the latest version patches those bugs.

Fix 6: Temporarily Disable Firewall and Antivirus

If none of the above fixes worked, your security software may be blocking DNS traffic. This is a surprisingly common cause, particularly with third-party antivirus suites like Avast, Kaspersky, and McAfee.

Temporarily disable your antivirus and firewall, then try loading a website. On Windows, you can disable the built-in firewall by going to Settings > Privacy and security > Windows Security > Firewall and network protection, then turning off the firewall for your active network.

If your DNS error disappears while the firewall or antivirus is disabled, you have found the culprit. Re-enable your security software immediately (do not leave it off), then add an exception for DNS traffic on port 53 in your antivirus settings. Most security programs have a settings section where you can whitelist specific ports or applications.

Why this works: security software inspects all incoming and outgoing traffic. If it incorrectly flags DNS queries as suspicious, it blocks them, and your browser cannot resolve any domain names. Adding an exception lets DNS traffic through while keeping the rest of your protection active.

Fix 7: Update Your Router Firmware

If all devices on your network show DNS errors and none of the device-level fixes have worked, the problem is likely your router. Outdated firmware can contain bugs that break DNS forwarding.

Log into your router’s admin panel by typing its IP address (usually 192.168.1.1 or 192.168.0.1) into your browser. Enter your admin username and password (check the sticker on your router if you do not know them).

Look for a “Firmware Update” or “System Update” section. This is typically found under “Advanced Settings” or “System Tools.” Click “Check for Update” and follow the prompts if a newer version is available. Do not unplug the router during the update process.

Why this works: router manufacturers release firmware updates to fix security vulnerabilities and bugs. A DNS-handling bug in an older firmware version could be silently dropping queries, and the update patches that specific issue.

After the update completes, restart your router and test your connection.

How to Change DNS Settings on Any Device

Changing your DNS server is the most effective long-term fix for DNS errors. You can do this on individual devices for quick testing, or on your router to apply the change network-wide. Here are the exact steps for every major operating system.

Windows 10 and Windows 11

Press Windows Key + I to open Settings. Go to “Network and Internet” and click on your active connection (WiFi or Ethernet). Scroll down and click “Properties” or click on the network name.

Find the “DNS server assignment” section and click “Edit.” Change the dropdown from “Automatic” to “Manual.” Toggle IPv4 on. Enter 8.8.8.8 as the preferred DNS and 8.8.4.4 as the alternate. Click “Save.”

For Windows 10, the path is slightly different. Go to Settings > Network and Internet > Change adapter options. Right-click your connection and select “Properties.” Select “Internet Protocol Version 4 (TCP/IPv4)” and click “Properties.” Choose “Use the following DNS server addresses” and enter 8.8.8.8 and 8.8.4.4.

MacOS

Open System Settings (or System Preferences on older versions). Click “Network” and select your active connection. Click “Details” (or “Advanced” on older macOS). Select the “DNS” tab.

Click the “+” button under DNS Servers and add 8.8.8.8. Click “+” again and add 1.1.1.1. You can add both Google and Cloudflare DNS for redundancy. Click “OK” and then “Apply.”

iPhone and iPad

Open Settings and tap “WiFi.” Tap the “i” icon next to your connected network. Scroll down to “Configure DNS” and tap it. Change from “Automatic” to “Manual.”

Delete any existing DNS servers, then tap “Add Server” and enter 8.8.8.8. Tap “Add Server” again and enter 8.8.4.4. Tap “Save” in the top right corner.

Android

Open Settings and tap “Network and Internet” (or “Connections” on Samsung devices). Tap “WiFi” and long-press your connected network. Select “Modify network.” Check “Advanced options.”

Change “IP settings” to “Static.” Scroll down to DNS 1 and enter 8.8.8.8. Enter 8.8.4.4 in DNS 2. Tap “Save.”

On newer Android versions (Android 9 and above), you can also use the system-wide “Private DNS” setting. Go to Settings > Network and Internet > Private DNS. Select “Custom provider hostname” and enter “dns.google” for Google DNS or “one.one.one.one” for Cloudflare.

Router-Level DNS Configuration

Changing DNS on individual devices works well, but it is tedious if you have many devices on your home network. A better approach is to set custom DNS servers at the router level. This applies your chosen DNS to every device that connects to your network automatically.

Router-level DNS is also more reliable because it ensures every device uses the same fast, dependable servers rather than mixing ISP DNS and public DNS across different devices.

How to Access Your Router Admin Panel

Find your router’s IP address. On Windows, open Command Prompt and type ipconfig. Look for “Default Gateway” under your active connection. That number (usually 192.168.1.1 or 192.168.0.1) is your router’s address.

On Mac, go to System Settings > Network, click your connection, then click “Details.” The router IP is listed under “Router.”

Type that IP address into your browser’s address bar. You will see a login page. Enter your admin credentials. If you never changed them, check the sticker on the bottom or back of your router for the default username and password.

Setting Custom DNS on Popular Router Brands

TP-Link routers: Go to “Advanced” > “Network” > “DHCP Server.” Look for “Primary DNS” and “Secondary DNS.” Enter 8.8.8.8 and 8.8.4.4 respectively. Save and restart the router.

Netgear routers: Go to “Advanced” > “Setup” > “Internet Setup.” Under “Domain Name Server (DNS) Address,” select “Use These DNS Servers.” Enter 8.8.8.8 and 8.8.4.4. Click “Apply.”

ASUS routers: Go to “WAN” under “Advanced Settings.” Under “WAN DNS Setting,” set “Connect to DNS Server automatically” to “No.” Enter 8.8.8.8 for DNS Server 1 and 1.1.1.1 for DNS Server 2. Click “Apply.”

Eero routers: Open the Eero app. Go to “Settings” > “Advanced” > “DNS Settings.” Select “Custom DNS.” Enter your preferred and alternate DNS servers. Save your changes.

ISP-Specific DNS Settings

If you prefer to use your ISP’s DNS servers (which are sometimes optimized for their network), here are the DNS addresses for common providers. Note that ISP DNS servers change occasionally, so verify on your provider’s support page.

Comcast Xfinity: 75.75.75.75 and 75.75.76.76

CenturyLink: 205.171.3.25 and 205.171.2.25

AT&T: Typically assigned automatically via DHCP. AT&T recommends using the automatically assigned servers.

Verizon Fios: 71.242.0.12 and 71.250.0.12

Spectrum: Usually auto-assigned. If you need static values, Spectrum recommends 208.67.222.222 and 208.67.220.220 (OpenDNS, which they own).

How to Prevent DNS Errors From Coming Back

One of the most frustrating things about DNS errors is that they tend to return. Many users report fixing the problem only to see it reappear days or weeks later. Here is how to make the fix permanent.

Set static DNS at the router level. Instead of relying on DHCP-assigned DNS (which can change when your router reboots or your ISP pushes new settings), manually set DNS servers in your router’s admin panel. This is the single most effective preventive measure.

Keep your router firmware updated. Check for firmware updates every few months. Most routers do not update automatically, so this requires manual attention. Some newer models support auto-updates, which you should enable if available.

Restart your router regularly. A simple reboot once a month clears accumulated cache issues before they cause problems. Set a calendar reminder if you need to.

Watch for Windows updates. Major Windows updates can reset network settings or conflict with network drivers. If a DNS error appears right after an update, check your DNS settings and network driver version.

When to Contact Your ISP

If you have tried every fix in this guide and the DNS error persists on all devices, the problem is likely on your ISP’s end. Contact their support line and report a DNS outage in your area. Ask specifically whether their DNS servers are experiencing issues.

If the error only affects one device despite all fixes, that device may have a hardware problem with its network adapter. In that case, a USB WiFi adapter can serve as a temporary workaround while you investigate the built-in adapter further.

FAQ’s

Conclusion

Fixing a DNS server not responding error on your home network comes down to three core actions: restart your equipment, flush your DNS cache, and switch to a reliable public DNS server. These steps resolve the problem in the vast majority of cases.

If the error returns, setting a static DNS at the router level is your best permanent solution. It applies to every device on your network at once and eliminates dependence on your ISP’s potentially unreliable DNS servers.

Remember that DNS issues are not a sign of a broken computer or router. They are a normal part of network troubleshooting, and with the right DNS configuration, they become rare. Work through the fixes in order, and you will be back online in minutes.