Flush your DNS first when one website points to the wrong place, loads an old version, or says “site not found” while everyone else can open it. It is fast, safe, and usually takes under a minute. On Windows, the command is ipconfig /flushdns [source: Microsoft].
TLDR: Flushing your DNS clears saved website address lookups from your device. A router restart resets your network box and may clear its own DNS memory, but it is a bigger hammer. Example: if your site moved to a new server at 2:00 PM and your laptop still opens the old one at 2:20 PM, a DNS flush may fix it in about 10 seconds. If every device in your home is slow or broken, restart the router instead.
Table of Contents
What DNS does, in plain human words
DNS is the internet’s phone book. You type example.com. DNS finds the matching server address, like 93.184.216.34. Your browser then knows where to go.
Without DNS, you would need to remember number strings for every site. Nobody wants that. I can barely remember where I put my charger.
Your computer, phone, browser, router, and internet provider may all save DNS answers. This saved info is called a DNS cache. Cache is useful. It makes repeat visits faster.
But cached DNS can get stale. That is when the trouble starts.
So, what does flushing your DNS do?
Flushing your DNS deletes your device’s saved DNS records. It does not delete files. It does not remove passwords. It does not reset your browser history. It just says, “Hey computer, stop using old address notes.”
After a flush, your device asks for fresh DNS info the next time you visit a site. If the old record was the problem, the site may start working right away.
Think of it like this:
- DNS cache: A sticky note with a website’s address.
- DNS flush: Throwing away the sticky note.
- Next visit: Asking for a new sticky note.
Honestly, it feels like magic when it works. One second your site is broken. Then you run one tiny command. Boom. The page appears. Annoying? Yes. Satisfying? Also yes.
When should you flush DNS?
Try a DNS flush when the issue feels specific. One domain is acting weird. Other sites are fine. Your internet is not totally dead.
Common signs include:
- A site moved servers, but you still see the old version.
- You changed DNS records for a domain.
- A domain shows “server not found.”
- Your coworker can open the site, but you cannot.
- Your browser keeps loading a parked page or wrong page.
- A login page redirects to an old address.
This happens a lot after domain changes. Web hosts tell you to “wait for propagation.” That phrase is technically fair, but it drives me crazy that it often hides a simple local cache issue.
DNS cache flush vs router restart
These two fixes are cousins. They are not twins.
| Fix | What it clears | Best for | How disruptive? |
|---|---|---|---|
| DNS flush | DNS records saved on one device | One website or domain being wrong | Very low |
| Router restart | Router session, possible router DNS cache, network state | Whole network problems | Medium |
A DNS flush is like cleaning one dirty window. A router restart is like turning the whole house power off and on. Useful sometimes. A bit dramatic, though.
What a router restart actually does
A router restart powers your router off and back on. This can fix many boring network gremlins.
It may:
- Clear the router’s temporary memory.
- Reset flaky Wi Fi behavior.
- Renew the connection to your internet provider.
- Pick up fresh network settings.
- Clear a DNS cache if the router keeps one.
But here is the part people miss. Restarting your router may not clear the DNS cache on your laptop or phone. Your device can still cling to its own stale record like a raccoon holding a snack.
So if the bad DNS answer lives on your computer, restarting the router may waste two or three minutes and fix nothing.
Which should you try first?
Use this simple order:
- Try another website. If all sites fail, it is not just DNS for one domain.
- Try another device. If only your laptop fails, flush DNS on that laptop.
- Flush DNS. It is quick and low risk.
- Restart the browser. Browsers also keep their own memories.
- Restart the router. Do this if many devices are affected.
- Check DNS records. The domain itself may be misconfigured.
If one site is broken on one device, flush DNS. If every site is broken on every device, restart the router. If one domain is broken worldwide, neither fix will save you. The domain settings need repair.
How to flush DNS on common devices
Windows:
ipconfig /flushdnsOpen Command Prompt as admin if needed. Run the command. You should see a success message.
macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderEnter your password when asked. The screen may not say much. That is normal.
Linux:
It depends on your DNS service. Try one of these:
sudo resolvectl flush-cachessudo systemctl restart systemd-resolvedChrome browser:
Type this into the address bar:
chrome://net-internals/#dnsThen clear the host cache. Chrome can be stubborn. It likes to keep its own little notebook.
Phone:
The easiest method is to toggle Airplane Mode on and off. You can also restart the phone. If you use a VPN, disconnect and reconnect it.
How to restart your router the right way
Do not mash buttons like you are defusing a movie bomb. Keep it simple.
- Unplug the router power cable.
- Wait 30 seconds.
- Plug it back in.
- Wait 2 to 5 minutes.
- Test the site again.
Avoid the reset button unless you know what it does. On many routers, holding reset wipes settings. That can remove your Wi Fi name and password. Fun? Not even a little.
Why domain issues happen after DNS changes
Domain records often have a TTL. That means “time to live.” It tells DNS systems how long they can keep an answer before asking again.
If a record has a TTL of 3600 seconds, that means 1 hour. Some caches may keep the old answer until that time ends. Some systems behave faster. Some act like they took a long lunch.
This is why two people can see different versions of the same site. One person has fresh DNS. Another has old DNS. Both swear they are right. Both might be.
When flushing DNS will not help
A DNS flush is handy. It is not a magic wand.
It will not fix:
- A website that is actually down.
- Wrong DNS records at the domain host.
- An expired domain.
- A broken web server.
- A bad SSL certificate.
- Firewall blocks.
- Parental control or security app blocks.
If the domain points to the wrong IP in public DNS, your cache is not the villain. The record itself is wrong. Fix the DNS record first. Then flush DNS to speed up testing.
Quick rule of thumb
Flush DNS when the problem follows a domain. Restart the router when the problem follows the whole network.
If your laptop alone opens the wrong site, flush DNS on the laptop. If every device at home is crawling, restart the router. If your phone works on mobile data but not on Wi Fi, the router or Wi Fi DNS settings may be involved.
Start small. Save the router restart for bigger messes. Your future self will enjoy those extra three minutes.