How to Flush DNS
Flush a stale DNS cache on Windows, macOS or Android, understand what the command changes, and know when DNS is not the real problem.
Kayla
Quetta Networks
Flushing DNS clears locally cached domain-name lookup results so the device must request fresh records. On Windows, run ipconfig /flushdns in Command Prompt. macOS commands vary by release. Android has no single universal user-facing flush button; reconnecting, restarting, or resetting the relevant app/network layer can force new lookups.
What does flushing DNS do?
DNS translates a domain such as example.com into an address a device can contact. Operating systems, browsers, routers and DNS resolvers may cache answers for a limited time. Flushing the device’s DNS cache discards its local reusable results; it does not change the website’s authoritative DNS records or repair its server.
Browser cache and DNS cache are different. Browser cache stores page resources. DNS cache stores name-resolution results. Read the browser-cache explanation if the page looks stale rather than the domain failing to resolve.
When should you flush DNS?
It is reasonable when:
A domain recently changed servers or DNS records.
The domain resolves on another device or network but not this one.
You see a DNS/name-resolution error.
A stale negative result may have cached a prior failure.
Trusted support instructions ask you to refresh the resolver cache.
It is unlikely to help when the website server is down, the connection is generally slow, a firewall or content filter blocks the request, a certificate is invalid, or the page’s cached CSS/JavaScript is stale.
How to flush DNS on Windows
Open Command Prompt.
Run:
Wait for the confirmation message.
Reopen the browser and test the domain.
Microsoft documents /flushdns as the option that flushes and resets the DNS client resolver cache in its official ipconfig reference.
This command does not erase browser history, cookies, saved passwords, or downloaded files.
How to flush DNS on macOS
macOS DNS-cache commands can change by release. A commonly used command on many modern versions is:
Enter the administrator password if prompted; Terminal does not display password characters. Because Apple can change resolver services, verify the command against documentation for your exact macOS version before publishing or executing it in a managed environment.
If you are not comfortable with Terminal, restart the Mac and network connection first. That is slower but avoids copying an unverified command for the wrong release.
How to refresh DNS on Android
Android does not expose one consistent “flush DNS” control across every manufacturer and release. Use the least disruptive sequence:
Turn Airplane mode on briefly, then turn it off.
Disconnect and reconnect the active Wi-Fi or mobile connection.
Close and reopen the browser.
Restart the phone if the problem remains.
If you configured Private DNS, verify the provider hostname and availability before changing it.
Clearing a browser or app cache is not guaranteed to clear every OS-level DNS result. Avoid Reset network settings until simpler tests fail, because it can remove saved Wi-Fi, Bluetooth, or other network configuration depending on the device.
Browser DNS caches and secure DNS
Some browsers maintain their own host or connection caches and may use encrypted DNS independently of the operating system. Browser-internal diagnostic pages can change or disappear between versions, so do not depend on an undocumented internal URL as the primary instruction.
If an OS-level flush does not change the result, fully close and reopen the browser, compare another browser, and check its Secure DNS/Private DNS setting.
Do not confuse flushing DNS with changing DNS providers
Flushing removes cached results. Changing a DNS provider selects a different resolver. The second action can affect privacy, filtering, availability, and network policy, so it should not be presented as the automatic next step.
For Android ad-filtering DNS specifically, use the separate AdGuard DNS setup guide. That page covers ad-blocking configuration; this page covers resolver-cache troubleshooting.
What to test after flushing DNS
Reopen the browser and enter the full domain directly.
Try another trusted domain.
Compare Wi-Fi and mobile data.
Check whether another device on the same network has the problem.
Disable one VPN or DNS-filtering layer temporarily, then restore it.
Check the website’s service status or authoritative DNS if you manage the domain.
If the site still fails, use the cache/DNS troubleshooting decision tree.
Where Quetta fits
Open the domain in Quetta and another browser on the same connection. If both fail identically, the issue is more likely outside a single browser. If only one fails, compare that browser’s Secure DNS, extensions, site permissions, and content filters.
Quetta may be named as one optional second-browser test, but this DNS article should not use a hard product CTA. Quetta cannot repair incorrect authoritative DNS records or a website outage.
Frequently asked questions
Is it safe to flush DNS?
Yes, flushing a local resolver cache is normally low risk. The device simply performs fresh lookups. It does not delete personal browser data.
Does flushing DNS make the internet faster?
Not generally. It can correct a stale or negative cached result, but fresh lookups may briefly add work. It is a troubleshooting action, not routine acceleration.
Does restarting a device flush DNS?
It often clears or refreshes local resolver state, although behavior differs by operating system, browser, and network layer.
Why does a site still fail after ipconfig /flushdns?
The problem may be at the browser, router, resolver, VPN, firewall, server or authoritative DNS layer. A Windows client-cache flush changes only one layer.
Is DNS cache the same as browser cache?
No. DNS cache stores domain lookups; browser cache stores reusable website resources such as images, scripts, and stylesheets.