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.
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:
Before trying fixes, run two commands to understand the problem. Open Command Prompt (press Windows + R, type cmd, press Enter):
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 firstnslookup 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 brokenWindows 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.
ipconfig /flushdnsNetwork 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:
netsh int ip resetnetsh winsock resetipconfig /releaseipconfig /renewipconfig /flushdnsRestart 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.
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.
ncpa.cpl, press Enter. This opens the Network Connections windowipconfig /flushdns to clear the old cacheIf 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.
Windows runs a service called DNS Client that handles DNS caching and resolution. If this service stops or malfunctions, DNS lookups fail.
services.msc, press EnterNote: 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.
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.
Some DNS issues occur because the system is trying to resolve names using IPv6 DNS, which may not be properly configured on your network.
ncpa.cpl)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.
If multiple devices on the same network have DNS problems, the issue is the router, not your computer.
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.
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.