Fix DNS Not Responding on Windows

Common causes of DNS failure on Windows

Before diving into fixes, understand what typically breaks DNS on Windows:

• Stale DNS cache — Windows caches lookups aggressively. Corrupt or expired entries block resolution.
• ISP DNS outage — Your ISP's default DNS servers may be overloaded or down.
• VPN or proxy interference — VPN clients often override DNS settings and may not restore them properly after disconnecting.
• Firewall blocking port 53 — Security software can silently block DNS traffic.
• Broken Winsock catalog — Malware removal or bad drivers can corrupt the network stack.

Step 1 — Check your internet connection

Open Command Prompt (Win+R, type cmd, press Enter) and run:

ping 1.1.1.1

If you see replies with round-trip times, your internet connection is working and the problem is specifically DNS. If the ping times out, your issue is the network link itself — check your cable, Wi-Fi, or router before continuing.

You can also try ping 8.8.8.8 as a second test. If one IP works but not the other, your ISP may be filtering traffic.

Step 2 — Flush the DNS cache

Open Command Prompt as Administrator (right-click, Run as administrator) and run:

ipconfig /flushdns

You should see: Successfully flushed the DNS Resolver Cache.

Then test resolution immediately:

nslookup example.com

If nslookup returns an IP address, the flush fixed the issue. If it returns "DNS request timed out", continue to the next step.

Step 3 — Reset Winsock catalog

The Winsock catalog manages how Windows applications communicate over the network. Corruption here can break DNS completely.

In an elevated Command Prompt, run:

netsh winsock reset

Then also reset the IP stack:

netsh int ip reset

Restart your computer after both commands. This resets the network stack to factory defaults without affecting your files or applications.

Step 4 — Release and renew IP address

Run these two commands in sequence in an elevated Command Prompt:

ipconfig /release

ipconfig /renew

This forces your network adapter to request a fresh IP address and DNS server configuration from your router's DHCP server. If your router recently changed DNS settings, this picks up the new values.

Step 5 — Switch to a public DNS server

Your ISP's DNS servers may be down or unreliable. Switching to a public resolver often fixes the problem immediately.

Via Settings (Windows 11):

1. Open Settings (Win+I) and go to Network & internet.
2. Click your active connection (Wi-Fi or Ethernet), then Hardware properties.
3. Click Edit next to DNS server assignment.
4. Switch to Manual, enable IPv4.
5. Enter 1.1.1.1 as Preferred DNS and 8.8.8.8 as Alternate DNS.
6. Click Save.

Via PowerShell:

Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ServerAddresses ("1.1.1.1","8.8.8.8")

Replace "Wi-Fi" with your adapter name. Run Get-NetAdapter to find it.

For a detailed walkthrough, see our Windows 11 DNS setup guide.

Step 6 — Disable IPv6 temporarily

Some ISPs have misconfigured IPv6 DNS servers. Disabling IPv6 forces Windows to use IPv4 DNS exclusively.

1. Press Win+R, type ncpa.cpl, press Enter.
2. Right-click your active adapter and choose Properties.
3. Uncheck Internet Protocol Version 6 (TCP/IPv6).
4. Click OK and test your connection.

If DNS works with IPv6 disabled, the issue is your ISP's IPv6 DNS infrastructure. Contact them or use a public DNS that supports IPv6 properly.

Step 7 — Check Windows Firewall and security software

DNS uses UDP port 53 (and sometimes TCP 53 for large responses). If a firewall blocks this port, no DNS queries can leave your machine.

Open Windows Defender Firewall with Advanced Security (wf.msc) and check:

• Outbound Rules — Look for any rule blocking port 53 or "all ports".
• Third-party software — Norton, Kaspersky, ESET, and Bitdefender all have built-in firewalls. Check their DNS filtering settings.

Quick test: temporarily disable your firewall entirely. If DNS works, add an exception for UDP/TCP port 53 and re-enable the firewall.

Step 8 — Run Windows network diagnostics

Windows 10: Right-click the network icon in the system tray and select Troubleshoot problems.

Windows 11: Go to Settings > System > Troubleshoot > Other troubleshooters > Network and Internet.

The diagnostics tool can detect and automatically fix common issues including DNS cache corruption, adapter misconfiguration, and DHCP failures.

Advanced troubleshooting with nslookup

If the steps above did not resolve your issue, use nslookup to diagnose exactly where DNS is failing:

nslookup example.com 1.1.1.1

This queries Cloudflare directly, bypassing your configured DNS. If it works, your configured DNS server is the problem. If it also fails, the issue is network-level.

Also check your hosts file at C:\Windows\System32\drivers\etc\hosts for entries that might override DNS for specific domains. Malware sometimes adds entries here to redirect traffic.

When to contact your ISP

Contact your ISP if:

• DNS fails even after switching to public DNS servers (1.1.1.1, 8.8.8.8).
• ping 1.1.1.1 fails (the problem is upstream, not DNS).
• The issue affects all devices on your network (not just one PC).
• DNS only fails at certain times of day (ISP overload).

Test your DNS configuration

After fixing DNS, verify your configuration is secure and performant:

• DNS Privacy Check — Test whether your DNS resolver supports DNSSEC, DoH/DoT, and detects leaks.
• DNS Gaming Benchmark — Measure latency to 50+ public DNS servers and find the fastest for your location.
• Browse all public DNS servers — Our live-tested directory of reliable resolvers worldwide.

Frequently asked questions

Why does DNS stop working after a Windows update?

Windows updates can reset network adapter settings, flush custom DNS configurations, or install new drivers that conflict with your network stack. After an update, check that your manual DNS settings are still in place and flush the DNS cache.

How do I know if the problem is DNS and not my internet?

Open Command Prompt and run ping 1.1.1.1. If you get replies, your internet connection works and the problem is DNS. If ping fails too, the issue is your network connection, router, or ISP.

Can antivirus software cause DNS failures?

Yes. Security suites like Norton, Kaspersky, and Bitdefender include DNS filtering or firewall components that can intercept or block DNS traffic. Try temporarily disabling your antivirus to test, then add exceptions for port 53 if that resolves it.

Should I use Google DNS or Cloudflare DNS?

Both are reliable. Cloudflare (1.1.1.1) is generally faster and has a stronger privacy policy. Google (8.8.8.8) has wider IPv6 support and longer track record. Use our DNS Gaming Benchmark to test which is fastest from your location.