Windows command guide
Reset the DNS Client service
Sometimes DNS problems are local to the client cache or service state rather than the router or the ISP. Restarting the DNS Client service can clear that local stale state quickly.
This guide is written around the specific symptom-command match for reset the dns client service, 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.
net stop dnscache
net start dnscache
ipconfig /flushdns
Best place to run it
Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.
Fast repair workflow
- Start from the exact symptom on this page: Only some websites fail or point to the wrong destination
- Run the network repair line exactly as shown: net stop dnscache net start dnscache 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 an elevated Command Prompt.
echo Starting targeted repair sequence...
net stop dnscache
net start dnscache
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 page targets bad local hostname resolution, stale DNS entries, and DNS cache behavior that survives browser restarts.
- Only some websites fail or point to the wrong destination.
- The problem persists across multiple browsers.
- A DNS flush alone did not fully clear the issue.
How the command works
Restarting the service resets the local resolver service, and flushdns clears the cached records Windows was using.
When it makes sense to run it
Use it when name resolution itself is clearly wrong on the PC.
Before you run this command
- Open an elevated Command Prompt or PowerShell window before running net stop dnscache net start dnscache ipconfig /flushdns.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: only some websites fail or point to the wrong destination.
- 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 net stop dnscache net start dnscache ipconfig /flushdns, compare the result against the symptom that brought you here. The most useful checkpoint is whether only some websites fail or point to the wrong destination 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 net stop dnscache net start dnscache ipconfig /flushdns is to repeat the action that previously triggered the problem. If the problem persists across multiple browsers 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.
Why administrator rights matter here
This command changes connectivity, DNS, IP, proxy, or adapter state. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.
Before you run it
Some enterprise systems use DNS-related policies or security tools. Expect them to rebuild DNS state afterward.
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 net stop dnscache net start dnscache ipconfig /flushdns does not improve only some websites fail or point to the wrong destination, 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 net stop dnscache net start dnscache 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 page targets bad local hostname resolution, stale DNS entries, and DNS cache behavior that survives browser restarts.
What should I check right after net stop dnscache net start dnscache ipconfig /flushdns?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether only some websites fail or point to the wrong destination becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on net stop dnscache net start dnscache 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.