Flushing DNS on phones, browsers and routers: the caches ipconfig does not reach

Domains & DNS·· 4 views· 4 min read

The short answer: ipconfig /flushdns and its Mac and Linux equivalents (they are in clearing the cache) only clear the operating system’s cache. The browser has its own, keeps connections already open to the old address, and may even ask a different resolver from the system’s (“secure DNS”). Phones and routers keep copies too. This article shows where those caches are and how to clear each one.

Where each cache lives, and how to clear it

Where How to clear it Note
Chrome, Edge, Brave, Opera Type chrome://net-internals/#dns in the address bar (in Edge, edge://net-internals/#dns) and press Clear host cache. Then, at chrome://net-internals/#sockets, press Flush socket pools. The second button closes connections already open to the old server, which would otherwise keep being reused.
Firefox Type about:networking#dns and press Clear DNS Cache. Firefox may have “DNS over HTTPS” switched on in its privacy settings.
Safari There is no page for it. Quit Safari completely (on a Mac, Cmd+Q) and flush the macOS cache. Closing the window is not enough: the program has to quit.
Android There is no command. Switch airplane mode on and off, or restart the phone. In Chrome for Android, chrome://net-internals/#dns works too. Check whether Private DNS is on in the network settings: it changes which resolver is used.
iPhone and iPad Switch airplane mode on and off, or restart. A VPN, a configuration profile or a manual DNS in the Wi-Fi settings change which resolver is used.
The router Restart it. Many routers keep a DNS cache and hand themselves out as the resolver for the whole network. If the whole home or office sees the old site and a phone on mobile data sees the new one, it is this layer or the provider’s resolver.

The order, from the inside out

1 First confirm the source already has the new value, as in the four places to check. If the source is wrong, clearing caches changes nothing.
2 Close the site’s tabs, then clear the browser’s name cache and its open connections (the table above).
3 Flush the operating system’s cache with the command in clearing the cache, and quit the browser completely.
4 Check whether the browser uses secure DNS. In Chrome and Edge look for “Use secure DNS” in the privacy and security settings; in Firefox, “DNS over HTTPS”. If it is on, the browser asks a different resolver from the terminal, and the two may disagree.
5 On the phone, airplane mode on and off; if it is still old, check Private DNS, the VPN and any manual DNS on the Wi-Fi.
6 If the whole network sees the old site, restart the router. If it still does, it is the internet provider’s resolver: that one only forgets when the old TTL runs out.
Clearing your caches does not clear your internet provider’s. If the resolver your network uses still holds the old answer, everything you clear on the computer gets the old one back. On a company computer, do not change the network’s DNS without talking to whoever runs the network.
The cleanest test of all: a phone on mobile data, with Wi-Fi off, in a private window. It is another device, another network and another resolver. Menu names change with the version and language of each system.

Cleared everything and only your network still sees the old site? Tell us the domain and what the phone on mobile data shows.

Open a support ticket

SEE ALSO

Clearing the cache: the browser’s, the computer’s, and the site’s

I changed the DNS and nothing shows yet: TTL, cache, and the four places to check

What DNS propagation really is: caches that expire, not a change that travels

Asking different DNS resolvers: how to read a propagation checker without panic

Testing a migrated site before you change the DNS (the hosts file)

Cloudflare: when it helps, how to switch it on, and the cache that fools you

RECOMMENDED PRODUCT

Register your .ao domain

Secure your company name before someone else registers it. from 30.000,00 Kz/yr

Search a domain
Was this answer helpful? Your answer helps us improve this article.