Windows command guide
ipconfig /flushdns Explained for Windows
Windows stores DNS results locally so websites and services can open faster the next time you visit them. That cache is useful until it becomes stale or incorrect. Flushing the DNS cache forces Windows to forget old name lookups and ask again.
This guide is written around the specific symptom-command match for flush broken dns cache, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
ipconfig /flushdns
Best place to run it
Command Prompt is the right execution context for this page. Even when elevation is not always required, using the right shell prevents syntax mistakes and makes the output easier to trust.
Fast repair workflow
- Start from the exact symptom on this page: A website works on another device but not on this computer
- Run the network repair line exactly as shown: ipconfig /flushdns.
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Disconnect and reconnect the adapter or reboot the PC if the reset changed saved network state.
- Verify raw connectivity, name resolution, and IP assignment before moving to router or driver troubleshooting.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
@echo off
echo Run this CMD sequence in the matching terminal window.
echo Starting targeted repair sequence...
ipconfig /flushdns
echo.
echo Review the output before closing this window.
pause
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
ipconfig /all
ping 1.1.1.1
nslookup example.com
What problem this command is trying to solve
This command targets stale or incorrect DNS cache entries stored on the local machine. It is often used when a site moved, a service changed IP, or the wrong destination keeps resolving.
- A website works on another device but not on this computer.
- The browser reaches an old server after a site change.
- Apps fail because name resolution seems outdated or inconsistent.
How the command works
ipconfig /flushdns clears the local DNS resolver cache in Windows. After that, Windows must perform fresh DNS lookups instead of relying on saved results.
When it makes sense to run it
Use it when the issue looks like a name resolution problem rather than a full internet outage. It is quick, low-risk, and often worth trying before more aggressive network resets.
Before you run this command
- Open the shell that matches ipconfig /flushdns before you paste it.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: a website works on another device but not on this computer.
- Check whether the failure is really system-wide and not just one website, one browser, or one Wi-Fi network.
What result to expect
After running ipconfig /flushdns, compare the result against the symptom that brought you here. The most useful checkpoint is whether a website works on another device but not on this computer becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after ipconfig /flushdns is to repeat the action that previously triggered the problem. If the browser reaches an old server after a site change still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Shell and execution context
This command usually does not need a full elevated repair context, but it still works best when you run it in the shell it was written for and read the output carefully.
Before you run it
This only clears the local DNS cache. If the issue comes from the router, ISP, or the website itself, flushing alone will not solve it.
When this is probably the wrong fix
This is not the right first fix when one website is down, the ISP has an outage, or only one app is blocked by a firewall rule. Use it when the Windows networking stack or saved network state looks damaged.
What to do if it does not help
If ipconfig /flushdns does not improve a website works on another device but not on this computer, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about connectivity, DNS, IP, proxy, or adapter state.
Frequently asked questions
Should I use ipconfig /flushdns for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: This command targets stale or incorrect DNS cache entries stored on the local machine. It is often used when a site moved, a service changed IP, or the wrong destination keeps resolving.
What should I check right after ipconfig /flushdns?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether a website works on another device but not on this computer becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on ipconfig /flushdns alone?
This is not the right first fix when one website is down, the ISP has an outage, or only one app is blocked by a firewall rule. Use it when the Windows networking stack or saved network state looks damaged.