Restart the router when multiple devices are affected; flush DNS when one device reaches the wrong site or cannot resolve a domain. A router restart clears temporary network state in the router, while a DNS cache flush clears saved name lookups on a computer, phone, or browser. On Windows, the ipconfig /flushdns command flushes and resets the DNS client resolver cache [source: Microsoft].
TLDR: If every phone, laptop, and smart TV is slow or offline, restart the router first. If only one device says a website cannot be found, or it keeps opening an old server after a site change, flush that device’s DNS cache. For example, if 6 devices are connected and only 1 laptop fails to load your bank’s website, a DNS flush is the cleaner first step. If all 6 devices lose internet at once, expect the router or ISP connection to be the real suspect.
Router restart vs DNS cache flush: the short version
A router restart clears temporary data held by the router. This can include active connection tables, DHCP leases in memory, DNS forwarding cache, and stale sessions. It also forces the router to reconnect to your modem or ISP gateway.
A DNS cache flush clears stored domain lookups. DNS turns names like example.com into IP addresses. Your device saves those answers for speed. That is usually helpful. It becomes annoying when the saved answer is wrong, expired, or points to an old server.
The practical rule is simple:
- Restart the router for whole-network issues.
- Flush DNS for one-device or one-website issues.
- Do both if the problem started after a router setting change, DNS provider change, or ISP outage.

What clearing router cache really means
Consumer routers rarely have a button labeled “clear cache.” That phrase usually means restart the router. When you reboot it, the router drops temporary entries and rebuilds them after it comes back online.
This can fix problems caused by:
- Stale NAT sessions, where the router tracks old connections badly.
- DHCP glitches, where devices do not get clean local IP addresses.
- DNS forwarding errors, where the router is acting as a DNS middleman.
- Memory leaks in cheap or aging router firmware.
- ISP reconnect issues after a brief outage.
The catch is that a restart is blunt. It disconnects everyone. Video calls drop. Downloads stop. Smart devices may take a few minutes to come back. Still, it is often the fastest fix when the entire home network is acting weird.
How to restart a router the right way
Do not jab the reset pinhole unless you want to erase settings. That is a factory reset, not a restart. It can wipe the Wi Fi name, password, port forwards, parental controls, and ISP settings.
Use this safer process:
- Unplug the router’s power cable.
- Wait 30 to 60 seconds. This gives volatile state time to clear.
- Plug it back in.
- Wait 2 to 5 minutes. The router needs time to boot and reconnect.
- Test two devices. Try one phone and one laptop if possible.
If you have a separate modem and router, restart them in order. Unplug both. Plug in the modem first. Wait until its internet light looks stable. Then plug in the router. This avoids the router asking for a connection before the modem is ready.
What a DNS cache flush does
A DNS cache flush tells your device to forget saved website lookup results. The next time you open a site, the device asks DNS again and stores a fresh answer.
This helps when:
- A website recently moved to a new server.
- Your browser says DNS_PROBE_FINISHED_NXDOMAIN.
- One device reaches an old version of a site.
- Only one app or computer has the problem.
- You changed DNS servers, such as from ISP DNS to Google DNS or Cloudflare DNS.
Honestly, it feels like DNS errors should be clearer. A site can fail in 3 seconds with a cryptic message, while every other site works fine. That often sends people to reset the router when the real fix is just clearing one local DNS cache.
DNS answers are normally kept only for a set time called TTL, or time to live. Google Public DNS explains that cached records expire according to TTL values set by domain owners [source: Google].

How to flush DNS on common devices
Windows
- Open Command Prompt as administrator.
- Type
ipconfig /flushdns. - Press Enter.
- Look for a message saying the DNS Resolver Cache was flushed.
macOS
Open Terminal and run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderEnter your Mac password if asked. You may not see a success message. That is normal.
Linux
The command depends on the DNS service. Common options include:
sudo systemd-resolve --flush-cachesor:
sudo resolvectl flush-cachesSome systems use nscd or dnsmasq. If one command fails, check which resolver your system uses.
Chrome and browser DNS cache
Browsers can keep their own DNS cache. In Chrome, enter this in the address bar:
chrome://net-internals/#dnsThen use the DNS clear option if available. Browser interfaces change, which drives me crazy when a fix takes 20 seconds longer than it should because the button moved again.
Which fix should you try first?
Use the symptom pattern. It is more reliable than guessing.
| Symptom | Best first action |
|---|---|
| All devices are offline | Restart router and modem |
| Only one laptop has trouble | Flush DNS on that laptop |
| Only one website fails | Flush DNS, then test another browser |
| Wi Fi connects but internet does not work | Restart router |
| Site changed hosting or DNS records | Flush DNS and wait for normal DNS expiry |
If you manage an office or shared network, avoid restarting the router during active work unless the outage is broad. A DNS flush on a single workstation is safer and faster. It also avoids breaking calls, payment terminals, printers, and file sync tools.
When neither fix works
If a router restart and DNS flush do not help, widen the check. The issue may not be cache at all.
- Check the ISP status page. There may be a local outage.
- Test with mobile data. If the site works there, your network path may be the issue.
- Try another DNS provider. Use a trusted public DNS service or your ISP default.
- Update router firmware. Old firmware can cause recurring drops.
- Inspect cables. A loose Ethernet cable can mimic a router fault.
- Check parental controls or security filters. They can block domains silently.

Best practice for reliable troubleshooting
Start small. Flush DNS when the problem is narrow. Restart the router when the problem is broad. Keep a short note of what you changed, especially DNS servers, router firmware, VPN settings, or security software.
For home users, a monthly router restart can help older hardware stay stable, but it should not be needed every day. If you must reboot daily, treat that as a warning sign. Check for overheating, failing power adapters, outdated firmware, or an overloaded router.
The clean troubleshooting order is: test another device, flush DNS if the issue is local, restart the router if the issue is network-wide, then check ISP and hardware causes. This keeps downtime low and avoids random fixes that only hide the real problem.
