Run Ipconfig Flushdns Windows 10
Run ipconfig /flushdns in Windows 10 from a Command Prompt or PowerShell window when a name lookup looks stale. If it works, test the site again. Skip that next step and you can waste time chasing browser or Wi‑Fi settings while the DNS fault stays in place. This guide shows when to flush DNS, what to try next if it fails, and how to tell local cache trouble from a wider network problem.
What ipconfig /flushdns does
ipconfig /flushdns clears the local DNS Resolver Cache on Windows 10. Windows stores recent hostname-to-IP lookups so it can answer repeat requests faster, and that cache includes the hostname, record type, and TTL data.
That cache can go stale after a DNS change. If a site moved to a new IP address or a web app changed records, your PC may keep trying the old answer until you flush it and force fresh DNS queries.
The flush only affects the local machine. It does not change the site, the router, or your ISP’s DNS records.
What changes after a flush
After the cache is cleared, Windows has to ask DNS servers again for the next lookup. That helps when a migrated site should now resolve to a different IP, or when a browser keeps landing on an address that no longer matches the current server.
Suppose a site moved from one host to another overnight and the old address now returns a 404. If your PC still has the old mapping cached, a flush can be the fastest way to force a fresh answer before you start changing anything else.
What the command does not touch
ipconfig /flushdns does not clear browser cache, does not reset your IP address, and does not fix a bad DNS server setting. If the outage is server-side or network-wide, the command will not repair it.
It also does not rewrite browser-specific DNS data. Chrome, for example, can keep its own DNS state separate from Windows.
When should you run it?
Run ipconfig /flushdns when the symptom looks like a stale name lookup, not a general hardware failure. It is a first-step triage move for a website that will not load, a migrated site that still resolves to an old IP, or a browser error that points to DNS rather than sign-in or content problems.
Website will not load
If a single site fails while other sites open, DNS is a reasonable first branch. If the error appears right after a domain move or DNS record change, flushing the cache is often the quickest test.
Old site IP after a move
Use it when a site or web app has been moved and you need your PC to stop using the old address. This is one of the clearest cases for a flush, especially when the server now answers at a different IP and the old path is no longer valid.
DNS_PROBE-style browser errors
Browser messages that mention DNS resolution, such as DNS_PROBE-style failures, are another good fit. They do not prove the problem is local, but they do justify a flush before you move to broader network steps.
Open a terminal in Windows 10
Open Command Prompt from Start, or press Win+R to open the Run box and type cmd, then press Enter. You can also use Windows PowerShell on modern Windows builds. The key point is simple: enter the command in a terminal window, not by assuming the Run dialog executes it directly.
Command Prompt from Start or win+R
From Start, search for Command Prompt and open it. If the command needs elevated rights in your environment, choose Run as administrator. In many cases, standard rights are enough for the flush itself, but the elevated window avoids permission trouble during related checks.
PowerShell on modern Windows
PowerShell can run ipconfig /flushdns on modern Windows, and modern builds also support Clear-DnsClientCache. If PowerShell is already open, either command can fit into the same troubleshooting path.
Why the command belongs in a terminal window
The Run box is useful for opening a terminal, but it is not the command line itself. That distinction matters because the flush command belongs in Command Prompt or PowerShell, where Windows can display the result and any error message clearly.
Run the flush command
Type ipconfig /flushdns and press Enter. Windows 10 supports this manual flush, and the usual result is a short success message that the DNS Resolver Cache was flushed.
What the success message looks like
The command prompt example usually appears at a path such as C:\Users\username, followed by the command and a short confirmation. If the command completes normally, that confirmation means the local cache was cleared and the next lookup should ask DNS again.
When admin rights matter
Admin rights are not a blanket requirement for every machine, but they can matter if the terminal is restricted or if you are pairing the flush with other network checks. If the command appears blocked, open an elevated Command Prompt or PowerShell window and try again.
Run ipconfig flushdns windows decision table
Use this table to decide whether the flush belongs in your next step, and what to do if the symptom stays after the command runs.
| Symptom | Run ipconfig /flushdns? | What to verify next | Next command if it fails |
|---|---|---|---|
| Website will not load in Windows 10 | Yes, if other sites still load and the error points to name lookup | Use nslookup to confirm the host resolves now | nslookup domainname |
| Old site IP after a migration | Yes, this is a strong first use case | Check whether the new IP appears after the flush | nslookup domainname |
| DNS_PROBE-style browser error | Yes, especially if the issue started after a DNS change | Compare browser behavior with a fresh resolver lookup | nslookup domainname |
| Browser-only failure on one site | Yes, but also clear the browser’s own DNS data | Check Chrome DNS cache separately from Windows cache | Clear-DnsClientCache or browser DNS clear path |
| Command succeeds but issue persists | Already done | Check DNS server settings, then renew IP or reset the network stack | ipconfig /release then ipconfig /renew |
| Command fails or seems to do nothing | Yes, but treat that as a sign to inspect the terminal setup | Check whether the DNS Client service is running and whether the window is elevated | services.msc or sc query dnscache |
How to read the table
If the failure is browser-only, Windows DNS may be fine and the browser’s own cache may be the real issue. If the flush works but the site still fails, move away from the cache and inspect DNS server settings or the broader network stack.
A common first-timer mistake is to stop after the success message. That message only proves the local cache was cleared; it does not prove the site’s DNS records, the router, or the browser are all in order.
Verify the result
After the flush, confirm that Windows now has to resolve names again. The easiest checks are ipconfig /displaydns and nslookup, which show whether the machine is holding old answers or pulling a fresh one.
Check cached entries with ipconfig /displaydns
ipconfig /displaydns shows the DNS entries currently stored on the PC. Right after a flush, you should see fewer entries or a fresh set built from new lookups rather than the old stale list.
Confirm a fresh lookup with nslookup
nslookup asks DNS directly for a hostname and shows the answer returned now. If the name resolves to the expected current IP after the flush, that is a strong sign the local cache was part of the problem.
What a normal result should show
A normal verification flow is simple: the cache empties, the next lookup repopulates it, and the returned address matches the current site or service. If the returned address still looks wrong, the issue is probably outside the local cache.
If the flush does not fix it
If ipconfig /flushdns succeeds but the symptom remains, move to DNS server checks, inspect the DNS Client service, and then renew IP or reset the network stack. At that point the problem is usually beyond a stale cache on your PC.
Check DNS server settings
Verify that the adapter is using the DNS servers you expect. A wrong or unreachable DNS server can keep returning bad answers even after the local cache is cleared.
Restart or inspect the DNS Client service
The DNS Client service, also called Dnscache, supports Windows DNS caching. If it is not running normally, cache-related troubleshooting may not behave as expected, so check the service state before moving on. (Wikipedia)
Move to renew IP or reset the network stack
If the site still will not load, try ipconfig /release and ipconfig /renew. If that still does not help, move to a broader network reset path rather than repeating the DNS flush.
Picture a laptop on Wi‑Fi that can open search pages but fails on one business portal after a server move. A DNS flush is the right first branch. If the portal still fails after a fresh nslookup, the next step is server, adapter, or DNS configuration work.
Frequently asked questions
What to do after ipconfig /flushdns
Test the site again, then verify with ipconfig /displaydns and nslookup. If the symptom persists, check DNS server settings, browser-specific DNS cache, and the DNS Client service before moving to IP renewal or a network reset.
When to use ipconfig /flushdns
Use it when a hostname may be stuck on an old answer, such as after a site migration, a DNS record change, or a DNS_PROBE-style browser error. It is a first-step check for local cache problems, not a fix for every connectivity issue.
Do I need admin rights to run ipconfig /flushdns?
Not always, but an elevated window can help if the command is blocked or if you are doing related network work in the same session. If the flush does not appear to run normally, reopen Command Prompt or PowerShell as administrator and retry.
Does ipconfig /flushdns clear browser DNS cache?
No. It clears Windows’ local DNS Resolver Cache only. Chrome and some other browsers may keep their own DNS state, so a browser-only failure can need a browser cache clear in addition to the Windows flush.
