Basics

11 reasons why DNS doesn’t work in Windows 10 (and how to fix it)

by Jonathan Dudamel
8 min read

A quick, actionable answer: if DNS doesn’t work in Windows 10, your PC can’t translate domain names (like example.com) to IP addresses, so web pages and online services fail even though the network might be up. This can be caused by corrupted DNS cache, wrong DNS settings, a broken network adapter, interference from VPNs/firewalls/antivirus, or DNS service problems. In this article you’ll learn 11 root causes and step-by-step fixes to get DNS resolving correctly again.

Contents show

Key Takeaway

Most DNS problems on Windows 10 are fixed by flushing the DNS cache, resetting the network stack, and temporarily switching to a reliable public DNS (like 8.8.8.8 or 1.1.1.1) to determine whether the issue is local or upstream.

Quick Fix Guide

Quick Fix Guide

Reason for the Problem Quick Solution
Corrupt DNS cache Run ipconfig /flushdns in an elevated Command Prompt.
Incorrect DNS server settings Set DNS manually to a known public DNS (e.g., 8.8.8.8, 8.8.4.4).
DNS Client service stopped Start or restart DNS Client in services.msc.
Network adapter glitch Disable and re-enable adapter or run Network reset.
Hosts file blocking entries Open C:\Windows\System32\drivers\etc\hosts and remove bad entries.
Firewall or antivirus blocking DNS Temporarily disable firewall/AV or create DNS allow rules.
VPN or proxy interference Disconnect VPN/proxy and retest DNS.
Stale DHCP lease Run ipconfig /release and ipconfig /renew.
Driver or Windows update issue Update or roll back network driver in Device Manager.
ISP DNS outage Switch to public DNS or contact ISP.
IPv6 or DNS-over-HTTPS conflict Disable IPv6 or browser DoH temporarily to test.

Detailed Fixes for “DNS doesn’t work in Windows 10”

1) Corrupt DNS cache

Why this causes the problem:
Windows stores DNS lookups in a local cache. If entries become corrupted or stale, your system may try to use invalid addresses.

Step-by-step solution:

  1. Open Start, type cmd, right-click Command Prompt and choose Run as administrator.
  2. Type: ipconfig /flushdns and press Enter.
  3. You should see “Successfully flushed the DNS Resolver Cache.” Try to browse again.
  4. If the issue persists, also run: ipconfig /registerdns and then ipconfig /renew.
See also  11 reasons why Wi-Fi 5GHz doesn’t work in Windows 10 (and how to fix it)

Tip: Flushing DNS is safe and often the fastest first step.

2) Incorrect DNS server settings

Why this causes the problem:
If the network adapter is pointing to an unreachable or misconfigured DNS server, name resolution fails.

Step-by-step solution:

  1. Open Settings > Network & Internet > Status and click Change adapter options.
  2. Right‑click your adapter (Ethernet/Wi‑Fi) and choose Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Choose Use the following DNS server addresses and enter 8.8.8.8 (Preferred) and 8.8.4.4 (Alternate) or 1.1.1.1 / 1.0.0.1.
  5. Click OK, close windows, and test browsing.

Note: Revert changes if you need to use a local DNS (corporate VPN) after testing.

3) DNS Client service stopped

Why this causes the problem:
The Windows DNS Client service (also called Dnscache) is required to manage DNS caching and queries locally. If stopped or disabled, name resolution can fail.

Step-by-step solution:

  1. Press Windows + R, type services.msc and press Enter.
  2. Find DNS Client, right-click and choose Properties.
  3. Set Startup type to Automatic and click Start if the service is not running.
  4. Click OK and test.

Tip: If the service won’t start, check Event Viewer (Windows Logs > System) for error codes.

4) Network adapter glitch

Why this causes the problem:
Temporary adapter issues (driver state, soft lockups) can break DNS lookups while basic connectivity remains.

Step-by-step solution:

  1. Open Settings > Network & Internet > Status.
  2. Click Network reset at the bottom, then click Reset now (this reinstalls network adapters and resets settings).
  3. Alternatively, open Control Panel > Network and Sharing Center > Change adapter settings, right‑click the adapter and choose Disable, wait 10 seconds, then Enable.
  4. Reboot the machine and test.

Warning: Network reset will remove saved Wi‑Fi networks and VPN clients; note credentials first.

5) Hosts file blocking entries

Why this causes the problem:
The local hosts file overrides DNS. Malicious or incorrect entries can redirect or block domains.

Step-by-step solution:

  1. Open Notepad as Administrator (right‑click, Run as administrator).
  2. In Notepad, open C:\Windows\System32\drivers\etc\hosts (set file type to All Files).
  3. Look for entries that map website names to IP addresses (e.g., 127.0.0.1 example.com) and remove suspicious lines or comment them by adding # at line start.
  4. Save the file and run ipconfig /flushdns.

Note: Legitimate local entries (e.g., development) may be present—remove only unwanted lines.

6) Firewall or antivirus blocking DNS

Why this causes the problem:
Security software may block DNS queries or intercept port 53 (UDP/TCP), preventing lookups.

Step-by-step solution:

  1. Temporarily disable your third‑party antivirus/firewall (consult software docs).
  2. In Windows Firewall, open Control Panel > System and Security > Windows Defender Firewall > Turn Windows Defender Firewall on or off and temporarily disable for testing.
  3. Test browsing. If DNS works, add firewall rules to allow DNS (outgoing UDP/TCP port 53) and allow your browser or DNS client.
  4. Re-enable protection and adjust rules rather than leaving security off.
See also  9 reasons why Shutdown doesn’t work in Windows 10 (and how to fix it)

Caution: Only disable security software temporarily for testing.

7) VPN or proxy interference

Why this causes the problem:
VPNs and proxies can force DNS to use remote servers or intercept queries—if they misconfigure or fail, DNS breaks.

Step-by-step solution:

  1. Disconnect any active VPN client and retry browsing.
  2. Open Settings > Network & Internet > Proxy and ensure Use a proxy server is off (unless required).
  3. If disconnecting fixes it, update or reinstall the VPN client, or configure split tunneling/DNS settings in the VPN.

Tip: Corporate VPNs often require company DNS; test with and without VPN to isolate.

8) Stale DHCP lease

Why this causes the problem:
A stale or incorrect DHCP lease can give wrong DNS servers to your PC.

Step-by-step solution:

  1. Open an elevated Command Prompt.
  2. Run ipconfig /release then ipconfig /renew.
  3. Run ipconfig /all to check the assigned DNS servers.
  4. If DNS servers shown are incorrect, set them manually (see Fix #2) or restart your router/DHCP server.

Note: Some routers need rebooting to issue correct DNS to clients.

9) Driver or Windows update issue

Why this causes the problem:
Bad network drivers or an update gone wrong may break DNS handling or the adapter’s network stack.

Step-by-step solution:

  1. Open Device Manager (Windows + X > Device Manager).
  2. Expand Network adapters, right‑click your adapter and choose Update driver. Try Search automatically for updated driver software.
  3. If the issue started after a driver update, choose Properties > Driver > Roll Back Driver.
  4. If unsure, download the latest driver from the manufacturer’s website and install.
  5. Reboot and test.

Tip: Use the adapter’s vendor (Intel, Realtek) driver rather than generic Microsoft drivers where possible.

10) ISP DNS outage

Why this causes the problem:
If your ISP’s DNS servers are down or misconfigured, all DNS queries will fail even though your local network is fine.

Step-by-step solution:

  1. Confirm by changing to a public DNS (see Fix #2) — if public DNS works, ISP DNS is the issue.
  2. Contact your ISP to report DNS outage and ask for ETA.
  3. Continue using a trusted public DNS or set router-level DNS to a public provider so all devices use it.

Note: Some ISPs intercept/redirect DNS; switching on the router often fixes this.

See also  13 reasons why Wi-Fi driver doesn’t work in Windows 10 (and how to fix it)

11) IPv6 or DNS-over-HTTPS conflict

Why this causes the problem:
If IPv6 is enabled but unsupported on your network, or if DNS-over-HTTPS (DoH) is misconfigured in the browser, DNS may behave unpredictably.

Step-by-step solution:
To disable IPv6 temporarily:

  1. Go to Control Panel > Network and Sharing Center > Change adapter settings.
  2. Right‑click your adapter, choose Properties, and uncheck Internet Protocol Version 6 (TCP/IPv6).
  3. Click OK and test.

To disable DoH in browsers:

  • Chrome: Visit chrome://settings/security and toggle Use Secure DNS off for testing.
  • Firefox: Open Options > General > Network Settings > Settings… and uncheck Enable DNS over HTTPS.

Tip: Re-enable IPv6 if your ISP or network uses it for full compatibility.

Additional tips and prevention

  • Use a stable public DNS (Google: 8.8.8.8, Cloudflare: 1.1.1.1) as a fallback on your router so all devices keep working during ISP DNS issues.
  • Keep network drivers updated and create a restore point before driver or system updates.
  • Regularly scan for malware; some malware changes DNS settings to intercept traffic.
  • If you manage many devices, centralize DNS with a local caching DNS server (Pi-hole, Windows Server DNS) to reduce dependency on external DNS.
  • Enable network logging (Event Viewer and router logs) when troubleshooting persistent issues.

FAQ

Q: How do I test whether DNS is the problem or my internet connection?
A: Ping an IP address (e.g., ping 8.8.8.8) — if that works but ping google.com fails, DNS is the issue.

Q: Can flushing DNS cause harm or data loss?
A: No — ipconfig /flushdns just clears cached name records; it’s safe and non-destructive.

Q: What if changing DNS to a public server fixes the issue — should I use it permanently?
A: You can use a public DNS permanently for reliability and privacy improvements, but in corporate networks follow your IT policy.

Q: Is DNS-over-HTTPS (DoH) recommended?
A: DoH can improve privacy by encrypting DNS; however, it can complicate troubleshooting and corporate DNS policies. Enable with understanding of consequences.

Q: When should I contact my ISP versus troubleshooting locally?
A: If multiple devices on the same network fail DNS and switching to public DNS on one device fixes it, the problem is likely ISP-side — contact your ISP.

Conclusion

Troubleshooting DNS issues requires methodical checks: flush the cache, check DNS server settings, reset the network stack, and isolate software that intercepts DNS (VPNs, firewalls, antivirus). Following the steps above will solve most cases where DNS doesn’t work in Windows 10 and help you determine whether the problem is local or with your ISP.

About the author

Jonathan Dudamel

Jonathan Dudamel

I'm Jonathan Dudamel, an experienced IT specialist and network engineer passionate about all things Windows. I have deep expertise in Microsoft project management, virtualization (VMware ESXi and Hyper-V), and Microsoft’s hybrid platform. I'm also skilled with Microsoft O365, Azure ADDS, and Windows Server environments from 2003 through 2022.

My strengths include Microsoft network infrastructure, VMware platforms, CMMS, ERP systems, and server administration (2016/2022).

View all posts

You may also like