Flush the Windows DNS cache first if only one Windows PC has trouble; restart the router if every phone, laptop, or smart TV is acting up. They fix different layers of the problem. Windows stores recent domain lookups locally, and Microsoft documents the ipconfig /flushdns command for clearing that resolver cache [source: Microsoft]. A router restart, on the other hand, refreshes the network box that hands out local addresses, manages traffic, and keeps your Wi-Fi radios running.
TLDR: If one Windows laptop refuses to open a site while your phone loads it fine, run ipconfig /flushdns first. It usually takes under 30 seconds and targets stale website lookup data, such as a saved old IP address for example.com. If 5 out of 6 devices are slow, dropping Wi-Fi, or showing “connected, no internet,” restart the router instead. In a small home office, that difference can save 10 minutes of unplugging gear when the real issue is just one stubborn PC.
What people call “Wi-Fi cache” is usually several caches
The phrase Wi-Fi cache sounds simple, but it hides a few different things. Your Windows PC may remember DNS answers. Your browser may cache pages. Your router may hold old DHCP leases, NAT sessions, ARP entries, and temporary routing data. Your internet provider may also cache DNS responses upstream.
So when someone says, “Clear the Wi-Fi cache,” the better question is: where is the stale information? If the wrong data lives on your Windows machine, restarting the router feels like swatting a fly with a couch. Honestly, it feels like overkill when a single command would have fixed it.
Windows DNS cache: what it does
DNS is the phone book of the internet. When you type a website name, Windows asks DNS servers for the matching IP address. To save time, Windows stores recent answers in a local DNS resolver cache.
That is usually helpful. Pages can start loading faster because Windows does not need to ask again every single time. But the cache can become annoying when a website changes servers, a domain record is updated, or a VPN changes how names should resolve.
Common signs that your Windows DNS cache may be the problem include:
- One website fails, but other sites load.
- The same site works on your phone, especially when the phone uses the same Wi-Fi.
- A site works in a VPN but not outside it, or the reverse.
- You recently changed DNS settings, hosts files, VPN software, or work network settings.
- You see DNS errors such as “DNS_PROBE_FINISHED” in the browser.
Clearing the DNS cache does not erase saved Wi-Fi passwords. It does not reset your router. It does not delete browser history. It simply tells Windows to forget stored domain lookup answers and ask again.
How to flush the DNS cache in Windows
Use this when the issue is limited to one Windows computer or one group of websites.
- Press Windows, type cmd.
- Right-click Command Prompt.
- Select Run as administrator.
- Type
ipconfig /flushdns. - Press Enter.
- Look for a message like Successfully flushed the DNS Resolver Cache.
Then close and reopen your browser. If the page still fails, try another browser too. Sometimes the browser has its own DNS or site cache sitting on top of Windows. Chrome, Edge, and Firefox can each hang on to their own bits of web data, which is deeply irritating when you already “fixed” the system cache.
Router restart: what it clears
A router restart is broader. It powers the device down, clears temporary memory, and forces it to rebuild active connections. On many home routers, this refreshes DHCP leases, NAT tables, Wi-Fi radio states, and temporary internal logs.
Restart the router when the problem affects the whole network. This includes phones, tablets, laptops, consoles, smart speakers, and TVs.
Typical signs that a router restart makes more sense:
- All devices are slow, not just one computer.
- Devices connect to Wi-Fi but have no internet.
- Wi-Fi disappears and comes back without warning.
- Video calls freeze across multiple devices.
- New devices cannot get an IP address.
- The router admin page feels sluggish or will not load.
How to restart a router the right way
Do not just jab the reset button unless you want a bad afternoon. The reset button can restore factory settings on many routers. That may wipe your Wi-Fi name, password, and custom settings. Expect to waste time recreating everything if you press it too long.
Use a simple power restart instead:
- Unplug the router power cable.
- If you have a separate modem, unplug that too.
- Wait 30 to 60 seconds.
- Plug the modem back in first, if separate.
- Wait until its internet light is stable.
- Plug the router back in.
- Wait 2 to 5 minutes for Wi-Fi to return.
After that, test with two devices. Open a simple website first. Then test the app or service that was failing. If only one device still misbehaves, the router probably was not the main issue.
Which should you try first?
Pick based on scope. That is the shortcut.
| Problem | Best first fix | Why |
|---|---|---|
| One Windows PC cannot open a site | Flush Windows DNS | Likely stale domain lookup data |
| Every device is slow | Restart router | Likely network-wide traffic or router issue |
| Wi-Fi keeps dropping | Restart router | Wi-Fi radio or firmware may be stuck |
| Only work sites fail after VPN use | Flush DNS | VPN DNS settings may have left bad entries |
| New devices cannot join properly | Restart router | DHCP or local address handling may be jammed |
A practical troubleshooting order
If you want a clean, low-effort process, use this order:
- Check scope. Test the same website on another device.
- Flush Windows DNS if only the Windows PC fails.
- Clear browser cache if the same browser keeps showing the issue.
- Restart the router if several devices fail.
- Restart the PC if DNS flushing did not help.
- Check DNS server settings if the issue keeps returning.
This order avoids needless downtime. A DNS flush is fast and local. A router restart kicks everyone offline for a few minutes. If someone is on a call, gaming, uploading files, or watching a movie, they will notice. They may also complain. Loudly.
When neither fix works
Sometimes the cache is not the villain. The website may be down. Your ISP may have a routing issue. Your DNS provider may be slow. Security software can also block traffic after an update. So can parental controls, firewall rules, and broken VPN clients.
Try these extra checks:
- Open the site on mobile data, not Wi-Fi.
- Try a different browser.
- Disable VPN briefly, then test again.
- Restart the Windows DNS Client service only if you know what you are doing.
- Check whether other users report the same site outage.
- Update router firmware if dropouts happen often.
If the problem returns every day, keep notes. Write down the time, affected devices, error messages, and what fixed it. Patterns matter. A router that needs daily restarts may be overheating, overloaded, or running buggy firmware. A Windows PC that keeps needing DNS flushes may have a VPN, security suite, or custom DNS setting causing repeated stale lookups.
The quick rule
One Windows device, one website, or DNS-looking errors: flush the Windows DNS cache. Many devices, weak Wi-Fi, or “connected, no internet”: restart the router. Both fixes are useful, but they are not the same tool. Use the smaller fix first when the problem is local, and save the router restart for network-wide trouble.