How to Fix DNS Not Resolving

2026-10-14 · Marion Remote Fix

When your computer cannot resolve DNS, you can connect to your network and your internet connection is technically working, but websites will not load. You see errors like "DNS_PROBE_FINISHED_NXDOMAIN," "Server DNS address could not be found," "This site can't be reached," or "DNS resolution failed." You can often still ping IP addresses directly (like ping 8.8.8.8) — the internet connection itself is fine, but the system that translates website names into IP addresses is broken.

What DNS does and why it breaks

DNS (Domain Name System) translates human-readable domain names like google.com into IP addresses like 142.250.80.46 that computers use to connect. When you type a URL in your browser, your computer asks a DNS server to look up the IP address, then connects to that IP. If the DNS lookup fails, your computer does not know where to send the request, and the page fails to load.

Common reasons DNS resolution stops working:

Quick diagnostic

Before trying fixes, run two commands to understand the problem. Open Command Prompt (press Windows + R, type cmd, press Enter):

  1. ping 8.8.8.8 — this pings Google's server by IP address, bypassing DNS entirely. If you get replies ("Reply from 8.8.8.8: bytes=32"), your internet connection works and the problem is DNS specifically. If this times out, the problem is your network connection, not DNS — troubleshoot your network first
  2. nslookup google.com — this asks your configured DNS server to resolve google.com. If it returns an IP address, DNS is working (the problem may be browser-specific). If it returns "DNS request timed out" or "can't find server," DNS resolution is confirmed broken

Fix 1: Flush the DNS cache

Windows caches DNS lookups locally so it does not have to query the DNS server for every website visit. If a cached entry is corrupted or stale, it can cause resolution failures for specific sites or all sites.

  1. Open Command Prompt as administrator (search for cmd, right-click, Run as administrator)
  2. Run: ipconfig /flushdns
  3. You should see "Successfully flushed the DNS Resolver Cache"
  4. Try loading a website. If it works, a stale cache entry was the problem

Fix 2: Reset TCP/IP and Winsock

Network configuration corruption can break DNS even though the rest of your connection works. Resetting the TCP/IP stack and Winsock catalog clears these settings to their defaults.

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

  1. netsh int ip reset
  2. netsh winsock reset
  3. ipconfig /release
  4. ipconfig /renew
  5. ipconfig /flushdns

Restart your computer after running all five commands. These commands reset your network configuration to defaults, so if you had manual IP settings, you will need to reconfigure them.

Fix 3: Change your DNS server

Your default DNS server is whatever your router assigns, which is usually your ISP's DNS server. ISP DNS servers can be slow, unreliable, or experiencing outages. Switching to a public DNS server often resolves the problem immediately and may also improve browsing speed.

Recommended public DNS servers

How to change DNS settings in Windows

  1. Press Windows + R, type ncpa.cpl, press Enter. This opens the Network Connections window
  2. Right-click your active network adapter (usually labeled Ethernet or Wi-Fi, whichever shows Connected) and select Properties
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties
  4. Select Use the following DNS server addresses
  5. Enter your chosen DNS servers. For Google DNS: Preferred = 8.8.8.8, Alternate = 8.8.4.4
  6. Click OK, then Close
  7. Open Command Prompt and run ipconfig /flushdns to clear the old cache
  8. Try loading a website

If the website loads with the new DNS server, the problem was your previous DNS server. You can leave these settings permanently — public DNS servers are generally faster and more reliable than ISP servers.

Fix 4: Restart the DNS Client service

Windows runs a service called DNS Client that handles DNS caching and resolution. If this service stops or malfunctions, DNS lookups fail.

  1. Press Windows + R, type services.msc, press Enter
  2. Scroll down to DNS Client
  3. Check the Status column. It should say Running. If it says anything else or is blank, right-click it and select Start
  4. Double-click DNS Client and verify the Startup type is set to Automatic. If it is set to Disabled, change it to Automatic and click Start, then OK

Note: On some Windows versions, the DNS Client service cannot be stopped or restarted from the Services console. If the Start and Restart options are grayed out, restart the computer instead — this forces the service to restart.

Fix 5: Check for VPN and proxy interference

VPN software and proxy configurations can redirect DNS traffic through their own servers. If the VPN is connected but its DNS server is unreachable, or if a proxy is configured but not functioning, DNS resolution fails.

Fix 6: Disable IPv6 temporarily

Some DNS issues occur because the system is trying to resolve names using IPv6 DNS, which may not be properly configured on your network.

  1. Open Network Connections (ncpa.cpl)
  2. Right-click your active adapter, select Properties
  3. Uncheck Internet Protocol Version 6 (TCP/IPv6)
  4. Click OK and test

If this fixes the problem, the issue is with your network's IPv6 DNS configuration. This is a common problem on networks where IPv6 is partially configured. You can leave IPv6 disabled on the adapter without affecting normal internet use — the vast majority of websites and services still work over IPv4.

Fix 7: Check your router

If multiple devices on the same network have DNS problems, the issue is the router, not your computer.

Fix 8: Scan for malware

Some malware changes your DNS settings to redirect traffic through malicious servers. If your DNS servers keep changing back to unfamiliar addresses after you set them, or if you are being redirected to unexpected websites, malware is likely involved.

  1. Run a full scan with Windows Defender (Windows Security, Virus and threat protection, Scan options, Full scan)
  2. Run a second scan with Malwarebytes (free version). It catches adware and potentially unwanted programs that Defender may miss
  3. After cleaning, reset your DNS settings as described in Fix 3 above and flush the cache

DNS troubleshooting in Marion

If your computer cannot resolve DNS and the fixes above have not helped, Marion Remote Fix can diagnose the problem remotely. DNS issues sometimes trace to network configuration, router problems, or ISP-level outages that require deeper investigation than basic troubleshooting covers.