Cache and DNS When an Address Looks Stale

Cache and DNS When an Address Looks Stale

TL;DR: When a lookup, a site, or a ping seems stuck on yesterday’s address, the usual culprits are a tab that never reloaded, a DNS resolver still holding an old answer, or a hosts file and a browser cache that disagree. The public IP of your connection and the address of a name you typed are different caches. Separate them, then refresh the one that is stale. A clean check is a reloaded page on Ipsaya, plus a DNS lookup you forced rather than remembered.

The intranet name that pointed at a funeral

A warehouse switched its time-clock vendor on a Friday. The old vendor’s name was updated in DNS to the new service at 6 p.m. On Monday a supervisor’s PC still opened the old clock, which had been replaced by a parking page. She concluded the cutover had failed and called the vendor, who correctly saw the new address from his own resolver. Her PC was using the office router for DNS, and the router had cached the old answer for longer than anyone expected. A phone on cellular, which did not use that router, showed the new site immediately. Nothing about her public IP was wrong. The name she typed was being answered by a memory.

Two caches people mash into one word

“My IP is cached” usually means one of three different stores. The browser tab is showing a page it fetched earlier and has not asked again. The operating system’s resolver, or the router’s, is repeating a DNS answer whose time-to-live has not expired, or has expired and stuck anyway. A local hosts file or a VPN’s private DNS is overriding the public name with an address from a lab. Only the first of these is fixed by reloading a what-is-my-IP page. The other two are about names, and reloading your own exit address will not move them.

  • Stale tab: reload, or open a new private window. If the number changes, the tab was the whole mystery.
  • Stale DNS: the name resolves to an old host. Your exit address can be current the entire time.
  • Hosts file or policy DNS: the PC is told a private answer on purpose. Flushing public cache will not override a file.
  • CDN pin: a new answer is still “old” in your head because you expected a single permanent server.

How to tell which store is lying

Reload the lookup in a private window. Note your exit address. Then resolve the troublesome name with a method that shows the answer explicitly, such as your operating system’s resolver query, and compare it with a public resolver’s answer if you know how to ask one. If your resolver and the public resolver disagree, you are holding a cached or overridden answer. If they agree and the site is still wrong, the server behind that address is the problem, and another flush will not create a new origin.

Routers cache for every device that uses them. A phone that works and a PC that does not, on the same Wi-Fi, can still differ if the PC has a VPN DNS or a hosts entry. A phone on cellular that works does not indict the PC’s IP address. It indicts the path the name took. The warehouse supervisor’s cellular success was the clean experiment.

Browser DNS and secure DNS

Some browsers resolve names themselves, ignoring the router, when a “secure DNS” setting is on. Two browsers on one PC can then see different versions of a newly moved site. That looks like madness until you remember they are two resolvers. Check the setting before you reinstall the browser. Turning it off and on again is a test. Leaving it off forever is a preference, not the first fix.

What a flush does not do

Clearing a DNS cache does not change your public IP. Rebooting the router might change the public IP and also clear the router’s DNS cache, which entangles two experiments. If you only needed a fresh name, reboot only after a resolver query has shown the cache is the culprit, and expect the public address to be a different question when the modem returns. If you only needed a fresh exit address, reload the lookup and do not touch DNS at all.

Captive portals add a nasty variant. They intercept the first queries after you join a Wi-Fi and can poison a negative cache so that a name fails until the portal is accepted. Sign in to the portal, then flush, then reload. Diagnosing the name before you click “I agree” wastes a perfectly good twenty minutes.

Ask which memory you are staring at

The time clock was fine. The router’s memory of its name was not. The next time a lookup and a website seem to argue, write down whether you are reading your exit address or a name’s address. Reload the first. Compare resolvers for the second. You will fix a smaller thing than “the internet is cached,” and you will stop rebooting a modem that was already telling the truth.

Similar Posts