This is the direct Windows 11 DNS cache clear page for people who want the exact command and the right place to run it.
Start here
Start with the fastest command or direct open action
This block comes first on purpose. Copy one command, open PowerShell, Windows Terminal, Run, or Start search, paste the exact text, press Enter, then do the slower click-by-click checks underneath only if you still need them.
Flush the DNS cache
Run this in: Command Prompt (Admin) or Windows TerminalAdmin: Yes
ipconfig /flushdns
What this command does
Clears the local DNS cache so Windows stops reusing an old name lookup result.
What to do after running it
Check the exact Windows page or result this guide mentions before moving to the next step.
Show current IP details
Run this in: Command Prompt (Admin) or Windows TerminalAdmin: Yes
ipconfig /all
What this command does
Runs the exact Windows action used in this guide so you do not have to guess the wording.
What to do after running it
Check the exact Windows page or result this guide mentions before moving to the next step.
Test a name lookup
Run this in: Windows Terminal or PowerShellAdmin: No
nslookup example.com
What this command does
Runs the exact Windows action used in this guide so you do not have to guess the wording.
What to do after running it
Check the exact Windows page or result this guide mentions before moving to the next step.
Open Command Prompt
Run this in: Start search or Run dialogAdmin: No
cmd.exe
What this command does
Runs the exact Windows action used in this guide so you do not have to guess the wording.
What to do after running it
Check the exact Windows page or result this guide mentions before moving to the next step.
Overview
What this guide helps you do
A stale local DNS cache can keep bad records longer than you want, especially after domain changes, local troubleshooting, or odd name resolution failures.
This changes the local DNS cache only.
It is quick and safe for common name-resolution checks.
It is often worth trying before bigger resets.
When to use this
When to use this guide
Useful when a website opens on another device but not this PC, or when a domain recently changed and Windows still seems to point to the old destination.
Before you start
What to review first
A DNS flush only clears the local resolver cache. It does not repair every network problem on its own.
Do this exactly
Open the right Windows area first, then follow the changes one by one
Press Start, type cmd or Terminal, and open Command Prompt or Windows Terminal. For a simple DNS flush, administrator rights are often not required.
Type ipconfig /flushdns exactly as shown and press Enter.
Wait for the message telling you that the DNS resolver cache was flushed successfully.
Close and reopen the browser or app that had the name-resolution problem so it asks Windows for fresh DNS information.
Test the same domain again. If the issue stays the same, move to larger network checks instead of repeating the DNS flush over and over.
Exact click path
Tell the user exactly what to open and press
Do not change ten things at once. Open the exact Windows page first, make one clear change, then check whether it solved the problem before moving on.
Fast open: Press Start, type cmd or Terminal, open Command Prompt or Windows Terminal, then type ipconfig /flushdns exactly and press Enter. Watch for the success message before you test the same website or service again.
Try a faster path
Useful when a website opens on another device but not this PC, or when a domain recently changed and Windows still seems to point to the old destination.