You run the Windows Network Diagnostics wizard, it spins for ten seconds, and then drops the unhelpful verdict: DNS server not responding. Your internet connection shows as active, every other device in the house works fine, but your Windows 10 machine refuses to resolve any domain name. This is one of the most common networking errors Windows users encounter, and while the message sounds severe, the fix is almost always straightforward once you know where to look. This guide covers every realistic cause in order of likelihood, with exact commands and click paths so you can get back online in minutes.
What the Error Actually Means
DNS (Domain Name System) translates human-readable hostnames like example.com into IP addresses that routers and servers understand. When Windows reports that the DNS server is not responding, it means your machine sent a query to the configured DNS resolver and received no valid reply within the timeout window. The result is that no website loads even though TCP/IP is technically connected. You might still be able to ping an IP address directly, which is a useful test to confirm the issue is purely DNS.
The root cause is almost always one of these five things: a stale or corrupted DNS cache, the wrong DNS server addresses configured on the adapter, a frozen DNS Client service, a misbehaving network adapter driver, or a problem with your router or ISP's resolver. Work through them in that order and you will solve it.
Step 1: Confirm It Is Truly a DNS Problem
Before changing anything, confirm the diagnosis. Open Command Prompt as Administrator (press Win + X, then click Windows Terminal (Admin) or Command Prompt (Admin)) and run these two commands:
If the first command succeeds (you see reply times) but the second fails with a server timed out or can't find server message, DNS is the confirmed culprit and your internet link itself is healthy. If both fail, the problem is deeper — a bad gateway, wrong IP assignment, or ISP outage — and DNS is a symptom, not the cause.
Step 2: Flush the DNS Cache and Reset the Resolver
Windows keeps a local DNS cache to speed up repeat lookups. If that cache becomes corrupted — which happens after sleep/wake cycles, abrupt shutdowns, or VPN disconnects — DNS queries start failing. Flushing it takes three seconds and fixes a surprising number of cases.
In the same elevated Command Prompt, run all four commands in sequence:
After the last command your adapter will briefly drop and re-acquire its IP from DHCP. Once it comes back, try loading a website. If it works, you are done. If not, continue to the next step.
Step 3: Reset TCP/IP and Winsock
Beyond the DNS cache, Windows maintains a Winsock catalog and TCP/IP stack that can get into a broken state, especially after installing VPN software, antivirus products with network filtering, or botched Windows Updates. Two commands reset both:
These commands write reset logs and require a full reboot to take effect. Restart, then test again before moving on.
Step 4: Switch to a Public DNS Server
Your router hands out its own IP address as the DNS server via DHCP. That works fine under normal conditions, but routers can lock up their DNS forwarder without affecting the rest of the network. The cleanest bypass is to hard-code a reliable public DNS address directly on your Windows adapter.
Go to Settings > Network and Internet > Change adapter options. Right-click your active adapter (usually Ethernet or Wi-Fi) and choose Properties. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties. Choose Use the following DNS server addresses and enter:
Those are Google's public resolvers. Alternatively use Cloudflare (1.1.1.1 / 1.0.0.1) or Quad9 (9.9.9.9 / 149.112.112.112). Click OK, close all dialogs, then open a browser and test. If sites load now, the fault is your router's resolver or your ISP's DNS — not Windows itself.
Step 5: Restart the DNS Client Service
Windows runs a background service called DNS Client (dnscache) that caches responses and forwards queries. If this service crashes or hangs, all DNS resolution stops system-wide. Restarting it is quick:
Press Win + R, type services.msc, and press Enter. Scroll down to DNS Client. Right-click it and look for Restart. Note: on many Windows 10 installations the Restart option is grayed out for this service. If that is the case, use the command line instead:
If the service refuses to stop, reboot the machine — Windows will restart it cleanly on boot.
Step 6: Check and Update the Network Adapter Driver
Outdated, corrupted, or poorly updated network adapter drivers are a frequent but overlooked cause of intermittent DNS failures on Windows 10, particularly after a major Windows Update. The OS updates can replace a manufacturer's optimized driver with a generic one that has known bugs.
Press Win + X and open Device Manager. Expand Network Adapters. Right-click your active adapter and choose Update driver > Search automatically for drivers. If Windows reports the driver is already current but you suspect otherwise, visit your adapter manufacturer's website directly (Intel, Realtek, Broadcom, or your laptop OEM's support page) and download the latest driver package manually.
After installing an updated driver, reboot and test DNS resolution. You can also try Roll Back Driver if the problems started right after a recent Windows Update — that option restores the previous driver version.
Step 7: Disable IPv6 on the Adapter
Windows 10 prefers IPv6 over IPv4 when both are available. If your router advertises an IPv6 DNS server address but does not actually have a functioning IPv6 path to the internet, every DNS query that goes out over IPv6 will time out before Windows falls back to IPv4. The symptom looks exactly like a DNS server not responding.
Go back to adapter Properties (same path as Step 4). In the list of items, uncheck Internet Protocol Version 6 (TCP/IPv6) and click OK. Test immediately. If this resolves the issue, the long-term fix is configuring your router to either properly serve IPv6 DNS or stop advertising an IPv6 prefix it cannot support.
Step 8: Check Your Router's DNS Settings
If hard-coding DNS in Step 4 fixed things, your router is forwarding DNS queries to a broken upstream server. Log in to your router's admin panel and check what DNS addresses it is using:
- Netgear: routerlogin.net or 192.168.1.1
- TP-Link: tplinkwifi.net or 192.168.0.1
- ASUS: asusrouter.com or 192.168.1.1
- Linksys / most others: 192.168.1.1 or 192.168.0.1
Navigate to your router's WAN or Internet settings. Look for the DNS section. If it shows your ISP's DNS addresses and those are the problem, replace them with 8.8.8.8 and 8.8.4.4 at the router level. This fixes every device on your network at once instead of configuring each machine separately. Save and reboot the router.
Step 9: Disable Security Software and VPN Clients Temporarily
Firewalls, antivirus products with DNS filtering (Bitdefender, Norton, Kaspersky, Avast), and VPN clients (especially ones that inject virtual network adapters) are notorious for intercepting or blocking DNS traffic. Temporarily disable your security software or disconnect the VPN, then test DNS. If resolution works with the software off, you have found the culprit. Check the software's DNS protection or "secure DNS" settings and either configure it properly or re-install a clean copy.
VPN software in particular creates virtual adapters that can have a lower metric than your real adapter, sending all DNS queries through a tunnel endpoint that is unreachable when the VPN is disconnected. Check adapter metrics by running:
Lower metric numbers mean higher priority. Your real physical adapter should have a lower metric number than any VPN virtual adapter when the VPN is not in use.
Step 10: Run the Windows Network Reset
If nothing above has worked, Windows 10 includes a nuclear-option network reset that reinstalls all network adapters and returns every networking component to its default state. You will lose saved Wi-Fi passwords and any manually configured adapter settings.
Go to Settings > Network and Internet > Status and scroll down to Network reset. Click it, read the warning, and click Reset now. Windows will reboot automatically. After restart, reconnect to your network and test DNS.
How to Verify DNS Is Working Correctly
Once you have applied a fix, do not just open a browser — browsers cache their own DNS. Verify at the command line:
The first command queries your currently configured DNS server. The second explicitly targets Google's resolver to rule out your local configuration. Both should return IP addresses instantly with no errors. You can also use our DNS Lookup tool to cross-check a domain from multiple external vantage points and confirm your fix is reflected globally.
How to Prevent This From Happening Again
A few proactive steps dramatically reduce the chance of this error recurring:
- Use a reliable public DNS resolver instead of relying entirely on your ISP's servers. Hard-code 1.1.1.1 and 8.8.8.8 on your router so every device benefits.
- Keep network adapter drivers current by checking your manufacturer's site after major Windows feature updates (21H2, 22H2, etc.).
- Reboot your router monthly. Consumer routers accumulate uptime-related bugs in their DNS forwarder. A reboot clears them.
- Avoid installing multiple VPN clients simultaneously. Each one adds a virtual adapter and can corrupt routing tables and DNS priority.
- Check Windows Update health. Pending updates that are stuck in a partially-applied state can break network components. Make sure updates complete cleanly or are properly rolled back.
When the Problem Is the ISP, Not Windows
Occasionally the error genuinely originates with your ISP. If switching to Google or Cloudflare DNS fixes the problem immediately (Step 4), contact your ISP and report that their DNS servers are unresponsive. Most ISPs have a status page where you can verify outages. This is more common than people expect during peak evening hours when ISP resolvers get hammered with traffic. Keeping a public DNS fallback configured is your permanent insurance against this scenario.
The DNS server not responding error on Windows 10 has a predictable set of causes and an equally predictable set of fixes. Start with the cache flush, move to changing DNS servers, and escalate through drivers and router settings if needed. The vast majority of users are back online after Step 2 or Step 4.