Windows: ipconfig /flushdns. Mac: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Linux (systemd): resolvectl flush-caches. Chrome: chrome://net-internals/#dns → Clear host cache.

The short explanation

Your operating system and browser cache DNS answers for a while so pages load faster. If a website changes IP address, or a wrong answer gets cached, you can end up at an old or broken address until the cache expires. Flushing forces a new lookup.

It’s safe and instant, but it won’t fix problems with your DNS server itself. For those, change DNS servers.

Symptoms

  • A site loads for others but not for you after it moved hosts.
  • DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED on specific sites.
  • You just changed DNS servers or the hosts file.

Why it happens

  • Stale or wrong cached DNS records.
  • Recently changed DNS settings or site hosting.

Try these fixes

  1. WindowsOpen Command Prompt and run ipconfig /flushdns. You'll see “Successfully flushed the DNS Resolver Cache”.
  2. macOSOpen Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (enter your password).
  3. LinuxOn systemd-resolved: resolvectl flush-caches (older: sudo systemd-resolve --flush-caches). With nscd: sudo systemctl restart nscd.
  4. Chrome and EdgeVisit chrome://net-internals/#dns → Clear host cache, then chrome://net-internals/#sockets → Flush socket pools.
  5. PhonesToggle Airplane mode on and off, or restart the phone.
  6. RouterRestarting the router clears its DNS cache too.

Command

ipconfig /flushdns

Windows Command Prompt. No administrator rights needed on most versions.

How to tell it worked: The site resolves to its current address and loads (check with nslookup sitename.com).

Avoiding it in future

If you flush DNS often, switch to a reliable resolver such as 1.1.1.1 or 8.8.8.8.