Flush the DNS cache first when one website will not load, points to the wrong server, or shows an old IP address. Restart the router only when several devices have DNS trouble, Wi Fi feels broken, or you suspect the router is handing out bad DNS settings. On Windows, the ipconfig /flushdns command clears the local DNS resolver cache, which is exactly the small local storage that may be holding stale domain data [source: Microsoft]. That small action often fixes the issue in seconds without kicking every phone, laptop, TV, and smart speaker off the network.

TLDR: Flushing DNS cache deletes saved domain lookups from your device, forcing it to ask for fresh DNS records the next time you visit a site. For example, if example.com moved to a new server and your laptop still remembers the old IP, a DNS flush can fix it in under 30 seconds. Restarting the router is broader and slower, but useful if multiple devices fail at once. In a small office with 12 laptops, flushing one affected laptop saves time; rebooting the router interrupts everyone.

What DNS Cache Actually Does

DNS is the phonebook system of the internet. You type a domain name, such as store.example.com, and DNS turns it into an IP address that computers can contact.

Your device does not want to ask the internet the same question every time. That would be slow and wasteful. So it stores recent DNS answers in a DNS cache. Your browser may keep one. Your operating system keeps one. Your router may keep one too. Your internet provider also runs DNS servers with their own memory.

This cache is usually helpful. Pages open faster. Apps connect without repeated lookups. The problem starts when the cached answer is wrong, old, poisoned, or tied to a failed lookup.

Honestly, it feels like the internet is gaslighting you when one site works on your phone but not on your laptop. The site is not always down. Your device may just be clinging to yesterday’s address.

What Flushing DNS Cache Does

A DNS cache flush clears stored DNS records from a device or browser. It does not delete passwords. It does not remove bookmarks. It does not reset your internet connection. It simply tells your system: “Forget the saved domain answers and ask again.”

After the flush, the next visit to a site may take a fraction longer. That is normal. Your device has to perform a fresh DNS lookup. After that, it builds a new cache.

Flushing DNS cache can help when:

  • A website recently changed hosting providers.
  • A domain’s DNS records were updated.
  • You see “server IP address could not be found.”
  • One site loads on mobile data but not on your computer.
  • You recently changed DNS providers, such as from ISP DNS to Google DNS or Cloudflare DNS.
  • You keep landing on an old version of a site.
  • A VPN or proxy was turned off, but sites still resolve oddly.

The key point is scope. A DNS flush usually affects one device. If your laptop has the stale record, flush the laptop. If Chrome has cached a bad DNS answer, clearing only the operating system cache may not be enough. Browser DNS cache can be stubborn. It drives me crazy that a browser can keep its own answer even after the system cache is cleared, adding another tiny trap to a simple fix.

DNS Cache Flush vs Router Restart

These two fixes are often treated as the same thing. They are not.

A DNS cache flush is precise. It targets saved DNS records on a device or app. It is fast. It does not disrupt other users. It is the cleaner first move when the problem is limited to one machine or one browser.

A router restart is wider. It resets the home or office gateway. It may refresh the WAN connection, clear some router memory, renew ISP settings, restart DHCP, and remove temporary glitches. It can also clear the router’s DNS forwarding cache if the router keeps one.

That wider reset has a price. Everyone gets disconnected. Video calls drop. Downloads stop. Security cameras may go offline for a minute or two. Smart devices may take longer to reconnect. Expect to waste time on the “why is the printer offline now?” side quest if your network is already fussy.

Use This Quick Decision Guide

  • Only one website fails on one device: flush DNS on that device first.
  • One browser fails, but another works: clear that browser’s DNS or browsing cache.
  • All websites fail on one device: check Wi Fi, DNS settings, VPN, and firewall before restarting the router.
  • Several devices fail at the same time: restart the router.
  • Devices connect to Wi Fi but show no internet: restart the router and modem.
  • A domain was just updated: flush DNS, then wait for DNS propagation if needed.

How to Flush DNS Cache

The exact steps depend on your system, but the idea is the same. Run a command or use a browser setting that clears stored DNS answers.

Windows:

  • Open Command Prompt as administrator.
  • Run: ipconfig /flushdns
  • Look for a success message.

macOS:

  • Open Terminal.
  • Use the correct command for your macOS version. Recent versions commonly use: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  • Enter your password if asked.

Linux:

  • The command depends on the resolver service.
  • For systems using systemd-resolved, try: sudo resolvectl flush-caches
  • For other setups, restart the DNS caching service in use.

Chrome-based browsers:

  • Open chrome://net-internals/#dns if available in your version.
  • Clear the host cache.
  • Restart the browser if the issue remains.

After flushing, test the domain again. If it still fails, try a private window, another browser, and another network. This separates DNS trouble from cookies, extensions, VPN rules, and broken site sessions.

When a Router Restart Is the Better Fix

Restart the router if the problem is not tied to one device. If three phones, two laptops, and a smart TV all struggle at once, your laptop’s DNS cache is probably not the villain.

A router restart can help when DHCP gets messy, the router stops forwarding DNS requests, or the ISP connection becomes unstable. It can also fix odd slowdowns caused by overloaded consumer routers. Some low-cost routers handle many devices poorly, especially with streaming, gaming, video calls, and smart home gear running together.

Do it properly:

  1. Unplug the router.
  2. If you have a separate modem, unplug that too.
  3. Wait 30 to 60 seconds.
  4. Plug in the modem first.
  5. Wait until it is fully online.
  6. Plug in the router.
  7. Test again after Wi Fi returns.

This is slower than a DNS flush, but it resets more moving parts. Use it when the problem is broad, not when one stubborn site is acting weird on one computer.

Why Domain Resolution Breaks After DNS Changes

Every DNS record has a TTL, or time to live. This tells resolvers how long they may keep the answer before asking again. A short TTL might be 300 seconds. A longer one may last hours. Some systems behave neatly. Others hold records longer than expected.

This is why a site migration can be messy. The new server is live. The DNS record is correct. Yet one user still reaches the old server. Another user sees the new site. A third gets an error. Same domain, different cached answers.

Flushing DNS removes your local piece of that confusion. It cannot force every DNS resolver on the internet to update instantly, but it makes sure your device is no longer the reason you are seeing stale results.

Best Fix Order

Use the least disruptive fix first:

  1. Reload the page. Simple, but worth doing.
  2. Try another browser. This catches browser-specific cache issues.
  3. Flush DNS on the device. Fast and targeted.
  4. Clear browser DNS or restart the browser. Especially useful for Chrome-based browsers.
  5. Switch DNS servers. Try a trusted public resolver if your ISP DNS is failing.
  6. Restart the router. Use this when several devices are affected.
  7. Call the ISP or hosting provider. Do this if the issue is still present across networks.

The practical rule is simple: flush DNS for a stale or wrong domain answer on one device. Restart the router for network-wide trouble. One is a scalpel. The other is a power cycle broom. Use the scalpel first, unless the whole house is already offline.

Scroll to Top
Scroll to Top