How to Flush DNS on Windows 10 and Windows 11 (ipconfig /flushdns)
Flushing DNS on Windows is a two-step process: open Command Prompt as administrator, run one command. Here is exactly how — plus what to do when it does not fix the problem.
What Is the Command to Flush DNS on Windows?
Open the Start menu. Type cmd. Right-click on Command Prompt and choose Run as administrator. Running as administrator is essential — the command fails silently without elevated permissions.
In the command prompt window, type:
ipconfig /flushdns
Press Enter. Success response: Windows IP Configuration. Successfully flushed the DNS Resolver Cache.
No restart required. The cache is cleared immediately.
Does Windows 11 Use the Same Command as Windows 10?
Yes. The command is identical on Windows 10 and Windows 11. Finding Command Prompt on Windows 11: press Windows + S, type cmd, right-click the result, choose Run as administrator.
How Do You Know DNS Was Actually the Problem?
Before flushing, it's worth confirming DNS is actually the issue rather than something else entirely. The classic signs: a site that used to load now shows "This site can't be reached" or a different site entirely than expected, a website works on your phone's mobile data but not on your Wi-Fi (or vice versa), or you just changed a domain's nameservers or DNS records and want your machine to pick up the new values immediately instead of waiting out the old TTL. If none of that matches — for example, the site is down for everyone, not just you — flushing your local cache won't help, because the problem isn't on your machine.
What Does ipconfig /flushdns Actually Do?
ipconfig /flushdns clears the Windows DNS Resolver Cache — the local store of recent domain name to IP address translations. After flushing, your device must fetch DNS records fresh from the configured DNS server for every domain. This ensures you get current records rather than cached ones that may be outdated. For more on what this means in practice, see what does flush DNS do.
Command Prompt vs PowerShell: Which Should You Use?
Command Prompt: ipconfig /flushdns
PowerShell alternative: Open PowerShell as administrator and run: Clear-DnsClientCache
PowerShell shows no success message — the absence of errors means it worked. Verify by running Get-DnsClientCache immediately after — an empty result confirms the cache is clear. Either works equally well; use whichever terminal you already have open.
What Are the Exact Steps, Start to Finish?
- Press Windows key
- Type: cmd
- Right-click Command Prompt
- Choose: Run as administrator
- Type: ipconfig /flushdns
- Press Enter
- See success message
Why Doesn't Flushing DNS Fix the Problem?
Not running as administrator. The command appears to succeed but does nothing without administrator elevation. This is the most common mistake.
Chrome has its own DNS cache. Go to chrome://net-internals/#dns and click Clear host cache. Then go to chrome://net-internals/#sockets and click Flush socket pools.
DNS propagation is still in progress. Flushing makes your device ask the server for fresh data — but if the server itself has not updated yet, you get the same old answer. Our DNS propagation guide explains how long changes take to spread.
The domain has expired. A site working yesterday but returning DNS errors today may have an expired domain name. Check WHOIS before spending time on cache troubleshooting.
Is There a Settings-Based Alternative to Command Prompt?
Windows 11 Settings: Settings, Network and internet, Advanced network settings, your active connection, More adapter options. There is no direct flush button here — use Command Prompt for the reliable ipconfig /flushdns approach.
Quick Answers
Never lose a domain again
Track every domain you own in one dashboard. Free for up to 15 domains.
