A co-worker sends you a link to a new web app. You click it, and your browser spins for 30 seconds before throwing a “DNS_PROBE_FINISHED_NXDOMAIN” error. You pick up your phone, connect to the same Wi‑Fi, and the page loads perfectly. When a website fails on one Windows PC but works on every other device in the room, a stale local DNS cache is very often the culprit. A fresh guide from Technobezz, published in July 2026, walks through the full troubleshooting chain, but for most Windows users the fix is a single command you can run right now: ipconfig /flushdns.

The DNS cache: a speed booster that occasionally backfires

Every time your browser visits a new domain, Windows asks a DNS server to translate the human‑readable name into a numeric IP address. That lookup takes a few hundred milliseconds. To avoid repeating that delay every time you reload the same page, Windows stores the answer temporarily in a local DNS resolver cache. The cache lasts only as long as the record’s time‑to‑live (TTL), but sometimes entries become corrupted, hang onto an address that has changed, or get poisoned by a misbehaving network device. When that happens, Windows trusts the stale local copy and never asks the live DNS server, causing “server not found” failures or repeated redirects to an old, dead IP.

The DNS Client service that manages this cache behaves identically on Windows 11 and Windows 10. No recent patch has altered the core mechanism; the commands that flush it have been stable for years. The July 2026 Technobezz article serves as a timely reminder because home routers, browser‑side encrypted DNS, and VPNs have made the diagnostic path more layered than it was even five years ago.

Is it really the DNS cache? Three quick tests before you open a terminal

Jumping straight to ipconfig /flushdns is often harmless, but if the problem isn’t in the local cache you’ll waste time. Run these checks in under a minute:

  • Same site, different device on the same Wi‑Fi / Ethernet. If a tablet or another laptop succeeds, the issue is local to your Windows PC. If every device fails, restart your modem and router first.
  • Same PC, different browser. If only Chrome fails while Firefox succeeds, the problem is inside Chrome’s own DNS cache or its Secure DNS (DoH) setting.
  • Same PC, phone hotspot instead of home Wi‑Fi. Connect the Windows PC to your phone’s mobile hotspot and retry. If the site loads, your router or ISP’s DNS is the bottleneck, not your local cache.

Use these results to decide whether to flush Windows DNS, restart network hardware, clear a browser’s cache, or contact your ISP.

The one‑line fix that still solves most cases

Microsoft has not changed the classic flush command in Windows 11. Here’s the fastest path:

  1. Save any open work—the flush itself doesn’t affect files, but it’s good practice before running anything elevated.
  2. Right‑click the Start button and select Terminal (Admin) or Command Prompt (Admin).
  3. Accept the UAC prompt.
  4. Type ipconfig /flushdns and press Enter.

You’ll immediately see: “Successfully flushed the DNS Resolver Cache.” That single operation wipes every cached name‑to‑address mapping the Windows DNS Client service was holding.

PowerShell users can achieve the same result with:

Clear-DnsClientCache

Microsoft’s documentation confirms the two commands are equivalent. There is no reboot required, no hidden background cleanup, and no need to stop the DNS Client service.

After the flush, open the failing website again. If it still fails, keep your command window open for the next diagnostic tier.

When flushing isn’t enough: extending the fix

A clean cache doesn’t guarantee a correct answer if the DNS server your PC is querying is still returning bad results. These steps address the next most common trouble spots.

Verify which DNS server Windows is using

In the same administrator command window, run:

nslookup example.com

Replace example.com with the domain that’s failing. The first line of output shows the server name and address that handled the query. If that server belongs to your ISP or a manually configured public resolver (like Google’s 8.8.8.8), you can continue. But if it’s a company‑specific or unknown address, and you’re on a personal device, it may indicate a rogue DNS redirection. For a deeper look, type:

ipconfig /all

Look under the active network adapter for DNS Servers. Ignore disconnected adapters unless you’re troubleshooting a VPN or virtual switch.

Renew your network lease when settings come from DHCP

If your PC obtains its TCP/IP settings automatically, a stale DHCP lease can hand out an outdated DNS server address. Run these three commands in order, all from an admin prompt:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

The first discards the current IP address, the second requests a fresh set of parameters (including DNS servers) from your router, and the third clears any lingering cache that referenced the old server. Reconnect to Wi‑Fi if Windows doesn’t reattach automatically, then test again.

Restart the router when multiple devices are affected

If every phone, laptop, and smart TV in the house sees the same DNS error, flushing your PC alone won’t fix it. Do this:

  1. Unplug the power cable from both your modem and router.
  2. Wait at least 30 seconds—this discharges residual memory in most consumer gear.
  3. Plug the modem back in and wait until its connection lights show a solid link.
  4. Plug the router back in and wait for it to finish booting.
  5. On your Windows PC, reconnect and run ipconfig /flushdns one more time.

If the symptoms return immediately on every device, the problem is likely with your ISP’s DNS service or a filtering/parental‑control feature on the router.

Inspect the Windows Hosts file for hard‑coded overrides

The Hosts file in C:\Windows\System32\drivers\etc can force a domain to a specific IP, and it overrides both the cache and external DNS. Entries here survive a cache flush. Open Notepad as administrator, navigate to the folder, set the file type filter to All Files, and open the file named hosts. Look for lines that contain the failed domain, such as:

203.0.113.10 example.com

If you’re sure the entry is obsolete and you are not on a domain‑managed PC, delete it, save the file, and flush DNS again.

Check browser‑level Secure DNS and VPN software

Chrome, Edge, and Firefox can all enable DNS over HTTPS (DoH), which bypasses the Windows DNS Client cache entirely and sends queries directly to a chosen resolver. If you flushed the system cache and the site still fails in one browser but works in another, the browser’s DoH setting is the likely cause.

  • In Chrome, open chrome://settings/security, scroll to Advanced, and toggle Use secure DNS off momentarily.
  • In Edge, visit edge://settings/privacy, look under Security, and turn off Use secure DNS.
  • In Firefox, go to Settings > Privacy & Security > DNS over HTTPS and select Off.

Restart the browser after the change. If the site loads, the browser’s DNS resolver is the issue; you can re‑enable the feature with a different provider or leave it off if you prefer the system‑level DNS. Also, temporarily disconnect any third‑party VPN or web filter. Many VPN clients install their own DNS drivers that can interfere.

When all else fails: the network reset

A full network reset is the nuclear option in Windows 11 and 10. It removes and reinstalls all network adapters, resets the Windows Firewall, and clears every cached network configuration—including DNS settings, static IPs, and stored VPN secrets. Because it is destructive, treat it as a last resort.

On Windows 11:
- Go to Settings > Network & internet > Advanced network settings
- Select Network reset and then Reset now
- Confirm, and let the PC restart
- Reconnect to your Wi‑Fi or Ethernet and test

On Windows 10:
- Settings > Network & Internet > Status > Network reset
- Click Reset now, then Yes

After the reboot, Windows will rebuild the network stack with factory defaults. If DNS errors persist even after this step, you’ve eliminated the PC as the cause; the next call is to your ISP or the website’s operator.

The DNS landscape is getting more complex, but the 30‑second flush still delivers

A decade ago, flushing the local cache fixed almost every name‑resolution hiccup. Today, multiple layers—router caches, ISP‑level redirects, browser DoH, corporate group policies, and even antivirus web shields—can all intercept or poison DNS replies. The fundamental troubleshooting logic hasn’t changed: isolate the layer, clear that layer’s stale data, and test again. For the vast majority of home Windows users, that first layer remains the operating system’s own DNS Client service, and the ipconfig /flushdns command sweeps it clean in seconds.

Keep in mind that business devices joined to Active Directory or protected by enterprise VPNs should never have their DNS settings manually overridden without IT’s approval. Switching to a public resolver on a workplace laptop can break access to internal file shares, printers, and sign‑in services. The same caution applies to school‑managed devices.

Outlook: what to watch as DNS evolves further

Microsoft is pushing deeper integration of DNS over HTTPS directly into Windows 11’s network settings, reducing reliance on browser‑specific toggles. When that arrives broadly, a single system‑wide DoH setting will simplify the diagnosis again, but it may also diffuse the cache across more locations (system, browser, router). For now, the old ipconfig /flushdns stalwart remains the first and fastest weapon against a cryptic “name not resolved” screen.