DNS address not found

You sit down, open your browser, and instead of your homepage you get that grey error page. "DNS address not found." You try refreshing. Same thing. You try a different site. Same thing. Sound familiar? I see this exact problem a dozen times a week through our remote support sessions, and the frustrating part is that half the guides out there tell you to do things in the wrong order, or skip the step that actually fixes it. So here's the real-world sequence that works, starting with the quickest wins and moving to the deeper stuff only if you need it.

What Actually Causes a DNS Address Not Found Error?

Before you start clicking things randomly, it helps to know what's actually going wrong. DNS (Domain Name System) is basically a phone book for the internet. When you type bbc.co.uk into your browser, your PC asks a DNS server "what's the IP address for that?" and the DNS server replies with something like 151.101.0.81. Your browser then connects to that IP. Simple enough. The DNS address not found error appears when that lookup fails, and it can fail for several different reasons.

The most common culprit is a dodgy or unreachable DNS server. Your router usually hands out a DNS server address automatically via DHCP, but if that server is offline, overloaded, or your ISP is having a bad day, every single website lookup will fail even though your actual internet connection is fine. I've seen this catch people out badly because their Wi-Fi shows as connected with full bars and they assume the problem must be something complicated.

Second most common: a stale or corrupted DNS cache. Your PC keeps a local cache of recent DNS lookups to speed things up. If an entry in that cache goes wrong, whether from a network blip, a VPN disconnecting badly, or a website changing its IP, your PC will keep serving up the wrong answer from cache even after the real problem is fixed. This is why ipconfig /flushdns is such a reliable first step.

Then there's Winsock and TCP/IP stack corruption. This sounds scary but it's more common than you'd think, especially after a Windows update goes a bit sideways or after installing certain VPNs or network accelerator software. The Winsock layer handles how Windows communicates with network protocols, and if it gets corrupted, DNS queries simply don't get sent correctly. You'll see this when the basic fixes don't work at all.

Other causes include a misconfigured network adapter (someone manually typed in the wrong DNS IP), a failed DHCP lease giving you a 169.254.x.x address, or your router or firewall blocking UDP port 53 which is the port DNS traffic uses. If you run ipconfig /all in Command Prompt and see a 169.254.x.x address, that's your immediate problem and you need to fix DHCP before anything else will work.

One quick sanity check before you do anything else: test whether other devices on the same network can browse. If your phone works fine on the same Wi-Fi, the problem is almost certainly local to your PC. If nothing works, the issue is likely your router or ISP. That distinction saves a lot of time.

DNS Address Not Found Quick Fixes

Start here. These take five to ten minutes and fix the problem more often than you'd expect.

More DNS Address Not Found Fixes: Intermediate Steps

These are the fixes I reach for most often during remote support sessions. They cover the majority of DNS address not found cases that the quick fixes don't catch. You'll need Command Prompt with administrator rights for some of these. Just search for "cmd" in the Start menu, right-click Command Prompt, and choose "Run as administrator".

If you're also dealing with Wi-Fi dropping out intermittently alongside this error, it's worth reading our guide to fixing Wi-Fi that keeps disconnecting, as an unstable connection can cause DNS failures that look identical to a DNS configuration problem.

Advanced DNS Address Not Found Fixes

These are for when the intermediate steps haven't worked. They touch deeper parts of Windows networking, so read each step before running it. None of them are dangerous, but they do change system settings that require a restart to take effect. The Winsock reset in particular is something I'd call a proper fix rather than a workaround. It addresses actual corruption in the network stack rather than just poking settings.

If you've been through all of these and you're still seeing DNS address not found errors on one specific website but everything else works, the problem is almost certainly on that website's end rather than yours. You can confirm this by running nslookup sitename.com 8.8.8.8 to query Google's DNS directly and see if it returns a valid IP. If it does, your DNS is fine. If you're also dealing with broader connectivity issues, our no internet access troubleshooting guide covers the network layer problems that can sit underneath DNS errors.

Preventing DNS Address Not Found Errors

Most of these errors are preventable. Here's what actually makes a difference, in order of importance.

1. Use a reliable public DNS server. Your ISP's DNS is often the weakest link. Switching to Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1) takes two minutes and makes a real difference to reliability. Keep IP assignment on automatic via DHCP though. Only the DNS server addresses need changing.

2. Flush your DNS cache after VPN sessions. VPNs are a very common cause of stale DNS entries. When you disconnect a VPN, it can leave behind cached entries that point to the VPN's internal DNS servers. Run ipconfig /flushdns after disconnecting and you'll avoid a lot of headaches. Some VPN clients do this automatically, many don't.

3. Keep Windows and network drivers updated. Outdated network adapter drivers are a genuine cause of DNS instability on some hardware. Check Device Manager periodically, especially after a major Windows update. If your adapter driver is more than a year old, it's worth updating it from the manufacturer's website rather than relying on Windows Update.

4. Be careful with network-touching software. Certain VPNs, proxy tools, and so-called network accelerators modify Winsock settings and can corrupt them if they're uninstalled badly. If you start seeing DNS address not found errors shortly after installing or removing something like that, Winsock reset is your first port of call.

5. Check your router's DNS settings. If multiple devices on your network keep getting DNS errors, the problem is almost certainly the router. Log into your router's admin panel (usually 192.168.1.1 or 192.168.0.1) and check what DNS servers it's configured to use. You can set Google or Cloudflare there too, which fixes the problem for every device on the network at once. Make sure UDP port 53 is not being blocked by any firewall rules while you're in there.

And if you're managing a work PC on a domain, keep an eye on the NCSI (Network Connectivity Status Indicator) settings. In enterprise environments, a misconfigured NCSI probe FQDN in the registry can make Windows report no connectivity even when DNS is working fine. That's a niche one, but it does come up.

DNS Address Not Found: Summary

The DNS address not found error is one of those problems that looks alarming but is almost always fixable without professional help, as long as you work through it in the right order. Start with the router restart and DNS cache flush. If those don't sort it, change your DNS server to Google or Cloudflare. If you're still stuck, release and renew your IP, then run the Winsock reset. The full network reset sequence covers every software-level cause in one pass. For the vast majority of people reading this, one of those steps will fix the DNS address not found error completely. If you've been through all of them and you're still stuck, that's when it's time to get a technician involved, because at that point you're likely looking at a router fault or an ISP issue that needs escalating.