Categories: HostKarle Support

ipconfig /flushdns: Flush DNS on Windows, Mac and Phone

ipconfig /flushdns clears the DNS resolver cache on a Windows computer, so the next lookup can request a fresh answer. This guide shows how to flush DNS on Windows, Mac, Android, iPhone and Chrome, then check whether your domain is resolving correctly after a nameserver or hosting change.

What you need before flushing DNS

You need the domain name that is giving you trouble, access to the device or browser where you see the old site, and a second way to check the result. If you recently moved a website, keep the correct nameservers or DNS records ready so you can compare them with the result.

Use this quick map:

Where the stale result may be storedWhat to refresh
Windows computerWindows DNS resolver cache with ipconfig /flushdns
MacmacOS DNS service, then reconnect or reopen the browser
Android or iPhoneReconnect the network or restart the device; there is no Windows-style universal command
ChromeChrome’s host cache and, if needed, its socket pool
Outside your deviceA public DNS lookup such as Google Admin Toolbox Dig

Flushing a local cache is safe for your website files and domain settings. It only makes that device ask for DNS information again; it does not edit your domain or force every DNS server on the internet to update immediately.

What flushing DNS does

DNS translates a domain such as example.com into an IP address or another DNS record. To avoid asking a DNS resolver for the same answer every time, your operating system, browser, router and internet provider may keep answers for a period set by the record’s time to live, or TTL.

Windows’ ipconfig /flushdns flushes and resets the DNS Client resolver cache. Microsoft also documents that the cache can include negative entries, such as a previous “domain not found” answer. Removing those entries is useful when a record has been corrected but your computer is still remembering the old response.

It does not do these things:

  1. Change nameservers at your registrar.
  2. Edit an A, AAAA, CNAME or MX record.
  3. Clear the cache held by your router, mobile operator, internet provider or a public resolver.
  4. Repair a website that has an application, SSL, hosting or server configuration problem.

That distinction matters after a host move. The command can make your computer query again, but an outside visitor may still receive a cached answer until the relevant DNS TTL expires.

Step 1: Run ipconfig /flushdns on Windows

Why: Use this when Windows opens an old website, shows a previous “server not found” result, or keeps resolving a domain to an earlier host.

  1. Save any work and open the Start menu.
  2. Type Command Prompt.
  3. Select Run as administrator. Approve the Windows permission prompt if it appears.
  4. Enter this command exactly, including the space before the slash:
   ipconfig /flushdns
  1. Press Enter.
  2. Close Command Prompt, then close and reopen the browser tab for the affected domain.

What success looks like: Windows should report, “Successfully flushed the DNS Resolver Cache.” The command normally completes quickly and does not change your Wi-Fi password, website files or domain records.

Microsoft lists /flushdns as the option for flushing the DNS client resolver cache in its official ipconfig documentation. If you want to inspect the cache before clearing it, run ipconfig /displaydns in Command Prompt.

If Windows says that ipconfig is not recognised, you are probably not in a normal Windows Command Prompt or PowerShell session. Open Command Prompt from Start and run the command again. If it says access is denied, reopen the window with Run as administrator.

Step 2: Flush DNS on a Mac

Why: macOS does not use the Windows ipconfig /flushdns command. Its DNS lookups are handled by macOS networking services, so use Terminal to ask the DNS responder to reload.

  1. Open Applications > Utilities > Terminal, or search for Terminal with Spotlight.
  2. Run:
   sudo killall -HUP mDNSResponder
  1. Type your Mac administrator password when prompted and press Return. The password will not appear on screen while you type.
  2. Quit and reopen the browser. If the domain is on Wi-Fi, disconnect and reconnect to that network if the old result remains.

What success looks like: Terminal may return to the prompt without a success message. Test the domain again in a new browser window or with dig example.com.

The exact DNS service details can vary between macOS releases. If the command returns an error or the issue affects every website, restart the Mac and reconnect to the network before trying more advanced changes. Do not change DNS server addresses just to flush a cache; that is a separate troubleshooting step.

Step 3: Refresh DNS on Android and iPhone

Why: Phones do not provide one cross-version equivalent of ipconfig /flushdns. Reconnecting the network is the least disruptive way to make the phone establish fresh network connections.

Android

  1. Turn Airplane mode on for about 10 seconds, then turn it off.
  2. Reconnect to Wi-Fi or mobile data.
  3. Open the affected website in a new browser tab.
  4. If the problem is limited to Chrome, open Settings > Apps > Chrome > Storage and cache and choose Clear cache. Menu names vary by Android version and phone maker.

What success looks like: the site loads with the current DNS answer. Clearing an app cache should not remove your photos or website files, but do not choose Clear storage unless you are willing to reset the app’s local data.

iPhone or iPad

  1. Open Settings > Wi-Fi.
  2. Tap the information button next to the connected network.
  3. Tap Forget This Network, confirm, and join the network again by entering its password. Use this only if a simple Wi-Fi off-and-on toggle does not help.
  4. If the issue continues across networks, restart the device and test again.

What success looks like: the site resolves in Safari or your other browser after the device reconnects. Apple says that resetting network settings removes saved Wi-Fi networks, passwords, VPN settings and other network configuration, so reserve Settings > General > Transfer or Reset [device] > Reset > Reset Network Settings for cases where simpler steps fail. Apple’s Wi-Fi troubleshooting guide explains this trade-off.

Step 4: Clear Chrome’s own DNS cache

Why: Flushing Windows or macOS does not necessarily remove an answer that Chrome has kept in its own host cache. Use this step when another browser opens the site correctly but Chrome still shows the old page or an old error.

  1. Open a new Chrome tab.
  2. Enter chrome://net-internals/#dns in the address bar.
  3. Select Clear host cache.
  4. Open chrome://net-internals/#sockets.
  5. Select Flush socket pools.
  6. Close every Chrome window and open Chrome again.

What success looks like: Chrome requests the domain again and shows the same result as another browser or a fresh private window. If the internal page is unavailable in your Chrome version, fully quit and reopen Chrome, then use Chrome’s normal browsing-data settings to clear cached files.

Do not start by deleting cookies or saved passwords. Those are different from the host cache and are usually unrelated to a nameserver change.

Step 5: Check the DNS answer outside your device

Why: A local flush cannot tell you whether the rest of the internet has received your new DNS configuration. An external lookup separates a local cache problem from a nameserver, record or propagation problem.

  1. Open Google Admin Toolbox Dig.
  2. Enter your domain without https://, for example example.com.
  3. Check the record type you changed: NS for nameservers, A or AAAA for an address, CNAME for an alias, or MX for email routing.
  4. Compare the answer with the DNS values shown in your registrar or hosting panel.
  5. Repeat the check from a different connection, such as mobile data instead of home Wi-Fi.

What success looks like: the public result shows the intended nameservers or record value, and the website opens from more than one network. If Google’s lookup and your device disagree, the local device or network may still have a cached answer. If several external lookups show the old answer, check the authoritative DNS settings and wait for the old record’s TTL to expire.

You can also use HostKarle’s WHOIS lookup to confirm that the domain is registered and inspect its basic registration information. WHOIS and DNS are different checks: a registered domain can still have incorrect or incomplete DNS records.

A browser may show a security verification page before the HostKarle WHOIS lookup loads.

When to flush DNS after moving a website

Flush the device cache after you have completed the actual domain change. For example, if you moved a WordPress website, first copy the site and database, verify the new hosting account, and then update the domain’s DNS or nameservers. The flush is the final local refresh, not the step that moves the website.

If you are moving to HostKarle, follow the guide to point your domain to hosting. If you need the correct delegation values, see how to find HostKarle nameservers and update them. For a WordPress move, keep the migration checklist in How to migrate your WordPress website manually open while you test the new site.

The order is:

  1. Confirm the new hosting account works.
  2. Update the authoritative nameservers or DNS record at the correct provider.
  3. Check NS, A, AAAA, CNAME or MX externally, depending on what you changed.
  4. Flush the local cache on the computer or phone that still shows the old result.
  5. Reopen the browser and test the website, HTTPS certificate and email separately.

Still seeing the old site?

Work through these checks in order:

  1. Check the record type. If you changed nameservers, inspect NS, not only the website’s A record. If the site uses IPv6, check AAAA as well as A.
  2. Check the browser. Try a private window or another browser after clearing the Chrome host cache.
  3. Check the network. Compare home Wi-Fi with mobile data. A router or ISP resolver can retain an answer after your computer has been flushed.
  4. Check the authoritative provider. Make sure the record was edited where the domain’s active nameservers point. Editing DNS at an old provider has no effect after a nameserver switch.
  5. Check the website separately. If external DNS already shows the new destination but the page fails, look at HTTPS, the hosting account, WordPress configuration or the application rather than repeatedly flushing DNS.
  6. Check email separately. A website may load while MX records still point to the previous mail service, or email may work while the website’s A record is wrong.

If Google’s public lookup has stale data after a recent registrar or DNS-host change, Google documents a Public DNS cache-flush tool. That refreshes Google Public DNS; it does not change your domain records or every resolver worldwide.

FAQ

What does ipconfig /flushdns do?

It clears the DNS Client resolver cache on Windows. The next time Windows needs an address for a domain, it can request a fresh answer from the configured DNS resolver. It does not edit your domain, nameservers or hosting account.

How often should I flush DNS?

Only flush it when you have a specific stale or incorrect DNS result to troubleshoot, such as after changing a record or moving a website. There is no benefit in running it on a routine schedule because normal cache expiry already refreshes DNS answers.

Does flushing DNS speed up propagation?

No. It refreshes the cache on your device only. Other resolvers still follow the TTL of their cached answer, so check the record externally and allow the relevant caches to expire after a nameserver or DNS change.

Why does the old website still open after I run the command?

The old answer may be cached by Chrome, your router, your ISP or an external DNS resolver. It may also mean the nameservers or DNS record were changed at the wrong provider. Compare the result from another browser, another network and an external DNS lookup before changing the record again.

Is there an ipconfig /flushdns command for Mac?

No. That is a Windows command. On macOS, open Terminal and run sudo killall -HUP mDNSResponder, then reopen the browser; restarting the Mac and reconnecting Wi-Fi are simpler fallbacks if the command does not help.

Samrat Ghosh

Samrat Ghosh writes hands-on guides about web hosting, WordPress, domains and email for Indian small businesses, students and freelancers - the practical documentation he wishes had existed when he set up his first website.

Share
Published by
Samrat Ghosh

Recent Posts

Zoho Mail Alternatives for Indian Businesses (2026)

Compare zoho mail alternatives for Indian businesses by rupee cost, IMAP access and mailbox limits,…

4 hours ago

Best Wix Alternatives in India for Small Businesses

Compare Wix alternatives for Indian small businesses: see 3-year rupee costs, WordPress hosting, migration limits,…

15 hours ago

Titan Email Price in India: Cost per Mailbox Explained

Titan email price in India explained with mailbox costs, features, team totals and a comparison…

21 hours ago

HostKarle vs Bluehost India: Price, Renewal and Panel

HostKarle vs Bluehost compares Indian shared hosting prices, renewal bills, email, SSL, backups, panels and…

1 day ago

Hindi Blog Kaise Banaye: WordPress Step-by-Step Guide

Learn how to write blog in hindi with WordPress, Hindi typing tools, domain and hosting…

2 days ago

Google Workspace Alternatives in India for Small Teams

Compare Google Workspace alternatives in India by yearly rupee cost, email features and migration effort…

2 days ago

This website uses cookies.