How to Flush DNS Cache on Windows, macOS, and Chrome
Your computer and browser can temporarily store DNS lookup results so websites can be reached more quickly.
Normally this cache is useful, but outdated or incorrect DNS information can sometimes cause websites to fail to load, redirect incorrectly, or continue pointing to an old server after DNS records have changed.
What is a DNS cache?
DNS translates domain names such as example.com into IP addresses that computers can use for network communication.
To avoid repeating the same DNS lookup every time you visit a website, operating systems, browsers, routers, and DNS resolvers may temporarily cache DNS results.
A cached entry normally remains available until its configured Time to Live (TTL) expires.
To understand the DNS system in more detail, read What Is DNS? .
Why would you flush the DNS cache?
Clearing the DNS cache can be useful when:
- a website recently changed servers or IP addresses,
- a domain works on one device but not another,
- you receive DNS-related errors,
- a website continues opening an old destination,
- you recently changed DNS settings,
- or you are troubleshooting a network problem.
Flushing the cache does not change a website's DNS records. It only removes locally stored results so fresh information can be requested.
How to flush DNS cache on Windows 11 and Windows 10
Windows provides a simple command for clearing its DNS resolver cache.
- Open the Start menu.
- Search for Command Prompt or Terminal.
- Open it.
- Type the following command:
Press Enter.
Windows should display a confirmation message indicating that the DNS resolver cache was successfully flushed.
Do I need Administrator mode on Windows?
On many Windows systems the command works from a normal Command Prompt, but some configurations may require elevated permissions.
If the command fails because of permissions:
- Search for Command Prompt.
- Choose Run as administrator.
- Run ipconfig /flushdns again.
How to flush DNS cache on macOS
macOS also maintains DNS-related caches, but the command used to clear them can vary between older versions of macOS.
On many modern versions of macOS, open Terminal and run:
You may be asked for your macOS administrator password.
The Terminal may not display a success message after the command completes. This is normal on many macOS versions.
How to clear DNS-related cache in Google Chrome
Chrome can maintain its own networking information in addition to the operating system's DNS cache.
If clearing the operating-system cache does not resolve a problem, restarting Chrome is often a useful first step.
You can also completely close all Chrome windows and reopen the browser so active browser networking sessions are recreated.
Chrome's internal diagnostic pages have changed over time, so older guides referring to specific internal DNS-cache buttons may not apply to every current version.
Should I restart the browser after flushing DNS?
It is often a good idea.
A browser may keep active connections, cached redirects, or other networking state independently of the operating system's DNS resolver cache.
After flushing DNS:
- close the affected browser,
- reopen it,
- and try the website again.
Does clearing the browser cache flush DNS?
Not necessarily.
A browser's ordinary cache usually stores website resources such as:
- images,
- CSS files,
- JavaScript files,
- and other downloaded web content.
The DNS resolver cache is a different type of cache.
Clearing browsing data may therefore not be the same as flushing the system DNS cache.
Does restarting the computer clear the DNS cache?
In many cases, restarting the operating system clears temporary DNS resolver information.
However, using the DNS flush command is usually faster than restarting the entire computer when DNS troubleshooting is the goal.
Does restarting the router clear DNS cache?
It depends on the router.
Some routers perform DNS forwarding or caching, while others simply send DNS queries to another resolver.
Restarting the router may clear some temporary state, but it is not a guaranteed substitute for clearing the cache on the computer itself.
What happens after you flush DNS?
After the local DNS cache is cleared, your device needs to perform new DNS lookups when domain names are requested again.
A simplified sequence might look like this:
- You enter a domain name in your browser.
- The system checks whether it already knows the DNS result.
- If the cache is empty, it contacts its configured DNS resolver.
- The resolver returns the current DNS information.
- The result may then be cached again temporarily.
Will flushing DNS make the internet faster?
Usually not.
DNS caching actually exists partly to make repeated lookups more efficient.
Clearing the cache is primarily a troubleshooting step rather than a general speed optimization.
Immediately after a flush, some domain names may even require a fresh lookup that was previously cached.
Will flushing DNS change my IP address?
No.
Clearing the DNS cache does not normally change:
- your public IP address,
- your private IP address,
- your router IP address,
- or the IP assigned by your ISP.
DNS resolution and IP address assignment are separate network functions.
You can see the public IP currently presented by your connection using the IPScope Public IP Lookup .
Will flushing DNS change my DNS server?
No.
Flushing the cache removes stored lookup results but does not normally change which DNS resolver your device is configured to use.
Your DNS resolver may still be provided by:
- your router,
- your ISP,
- a public DNS provider,
- a VPN,
- or an administrator-managed network.
What is DNS propagation?
When a website owner changes a DNS record, different DNS resolvers may continue using previously cached values until their TTL expires.
This is commonly described as DNS propagation, although the process is largely the result of caches expiring at different times.
Flushing your local DNS cache removes one layer of caching, but it cannot force every DNS resolver on the internet to discard its cached records.
Why does a website still show the old server after flushing DNS?
Several other layers may still contain older information.
Possibilities include:
- the recursive DNS resolver still has the old record cached,
- the website itself is cached by a CDN,
- the browser is using an active connection,
- the DNS record has not actually changed everywhere,
- or the site owner configured the DNS records incorrectly.
How can I check current DNS records?
You can query DNS records instead of relying only on what a browser currently displays.
The IPScope Network Toolbox includes a DNS Lookup tool that can query common DNS record types.
This can help when checking whether a domain currently resolves to the expected address or record.
What DNS records can affect a website?
Several DNS record types may be involved in website and network operation.
Common examples include:
- A — maps a name to an IPv4 address,
- AAAA — maps a name to an IPv6 address,
- CNAME — creates an alias to another hostname,
- NS — identifies authoritative name servers,
- MX — identifies mail servers,
- TXT — stores text-based information used for several purposes.
We will cover these record types in more detail in a separate IPScope guide.
DNS cache troubleshooting checklist
If a website is not resolving correctly, try these steps in order:
- Confirm that the website address is correct.
- Try another browser.
- Flush the operating-system DNS cache.
- Restart the browser.
- Check the domain's current DNS records.
- Try another network if available.
- Check whether the DNS resolver itself is experiencing a problem.
DNS cache FAQ
Is it safe to flush the DNS cache?
Yes. Clearing the local DNS resolver cache is a normal troubleshooting action. Fresh DNS information will be requested when needed.
Will I lose passwords or browser history?
No. Flushing the operating-system DNS cache does not delete browser passwords, browsing history, bookmarks, or personal files.
How often should I flush DNS?
There is normally no need to do it regularly. DNS caches are designed to manage themselves according to expiration times.
Should I flush DNS after changing a domain's DNS records?
It can be useful if your computer is still using an older cached result, but other DNS resolvers may continue using their own cached records until their TTL expires.
Does flushing DNS fix every website connection problem?
No. Website problems can also involve routing, servers, firewalls, browsers, TLS certificates, domain configuration, or internet connectivity.
Flushing the DNS cache removes locally stored DNS lookup results and forces your device to request fresh information when resolving domain names again. It is especially useful after DNS changes or when troubleshooting incorrect or outdated domain resolution.
Related IPScope guides
Learn how domain-name resolution works in What Is DNS? .
Learn the addressing system DNS ultimately resolves to in What Is an IP Address? .
Compare IPv4 and IPv6 addresses in IPv4 vs IPv6 .
Or open the IPScope Network Toolbox to perform a DNS lookup.
