how to help users clear DNS cache on Windows

TL;DR

Stale DNS makes a moved or updated site unreachable from one machine while the rest of the world loads it fine. On Windows, the fix is opening Command Prompt as administrator and running the flush command, then clearing the browser's internal DNS cache too. It takes 60 seconds and fixes a whole class of "the site is down for me but not for you" tickets. Only bother when DNS actually changed recently.

The query

how to help users clear DNS cache on Windows

Use this when

• Users hit stale DNS after a site move or record change
• "Site loads for others but not me" tickets
• Writing network troubleshooting guides
• New DNS records not resolving for some users

Not for

• DNS server administration
• Router configuration
• Mac or Linux instructions
• General "internet is slow" complaints

Steps

1. Confirm it is actually a DNS problem

Ask: does the site load on their phone (different network)? Did the site recently move or change hosts? If nothing DNS-related changed, flushing the cache wastes everyone's time. Rule it in first.

Expected output: DNS staleness confirmed as plausible.

2. Flush the Windows DNS cache

Walk them through it plainly: press the Windows key, type "cmd", right-click Command Prompt, choose Run as administrator, type the flush command, press Enter. They should see a confirmation message. Keep the instructions literal; non-technical users follow steps, not concepts.

Expected output: the success confirmation message.

3. Clear the browser's DNS cache too

Browsers keep their own DNS cache separate from Windows. Have them open the browser's internal network diagnostics page and clear the host cache there, or simply close and reopen the browser. Both caches must be fresh.

Expected output: browser DNS cache cleared.

4. Verify with a fresh lookup

Have them reload the site. If it loads, done. If not, check whether the new DNS records have actually propagated worldwide yet: changes can take hours. Do not flush repeatedly; it will not speed up propagation.

Expected output: site loads, or propagation identified as the wait.

Template: the walkthrough

This sounds like your computer remembering the old address for [site], [Name]. Let us clear that memory. Takes about a minute:

1. Press the Windows key and type: cmd
2. Right-click "Command Prompt" and choose "Run as administrator" (click Yes if it asks).
3. Type exactly: ipconfig /flushdns
   then press Enter. You should see "Successfully flushed the DNS Resolver Cache."
4. Now close your browser completely and reopen it. (Browsers keep their own copy of the address.)
5. Try [site] again.

If it still does not load, the new address may still be spreading across the internet, which can take a few hours. Let me know what you see after step 5.

Variant phrasings

flush dns windows 11

Step 2. Same command; the steps to open an admin prompt differ slightly by version.

website not loading after dns change

Steps 1 and 4. Confirm DNS is the issue, then set expectations on propagation.

clear dns cache chrome windows

Step 3. The browser cache is separate from the Windows cache.

Why it works

DNS resolvers cache answers for the record's TTL, and clients cache on top of that. After a move, the old answer lingers on the user's machine while the world sees the new one. Flushing drops the stale answer and forces a fresh lookup. It is the correct fix precisely when the symptom is "works everywhere except this machine."

Edge cases

• Corporate DNS: the company's resolver may cache beyond the user's machine. Flushing locally does nothing; IT must flush or wait.
• VPNs: the VPN's DNS overrides local. Disconnect to test, or flush while connected per the VPN's docs.
• The hosts file: a hardcoded entry overrides DNS entirely. Rare, but check if flushing never helps.
• Propagation impatience: if the change is under a few hours old, say so. No amount of flushing hurries the internet.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstfoC-pBS7Zw6-xTQnMSXgQ