You’ve been refreshing the terminal for 45 minutes. Your DNS change should have propagated by now. You open another website — still showing the old IP. The frustration is real, and it’s been wasting your time for years.
I’m here to tell you something uncomfortable: DNS propagation does not exist. It never did. And believing it does is actively making you a worse engineer.
A new tool called DNSGlobe puts this lie on full display. It’s a terminal-based app that visually shows you how DNS resolvers around the world respond to your record changes in real time. But if you watch it long enough, you’ll notice something odd: the updates don’t spread like a wave from source to edge. They pop up randomly, in arbitrary order, like popcorn across a map.
That’s because the underlying mechanism has nothing to do with ‘propagation.’ Every DNS resolver holds onto old cached records until their TTL expires. When you update your DNS, you’re not sending new data anywhere. You’re simply waiting for each resolver to forget the old data on its own schedule. And since every resolver has a different cache, a different TTL, and a different clock, the order is completely random.
The tool is brilliant, but not for the reason its creators think. It’s not a utility for monitoring propagation — it’s an educational tool that forces you to confront the myth head-on. Watching those dots turn green on the globe is watching the lie die in real time.
So why do we keep using the word ‘propagation’? Because it sounds like physics. Like a wave traveling across the ocean. It makes us feel like the internet is a coherent, orderly system. But the internet is chaos. DNS is chaos. And your workflow should reflect that.
Stop waiting. Start querying. The next time you make a DNS change, don’t sit there refreshing the same dig command. Query multiple resolvers directly. Use DNSGlobe. Or just accept that the old record will disappear when it feels like it, and build your deployment pipeline around that reality.
The myth dies today. If you share nothing else from this article, share this: DNS doesn’t propagate. It expires. Plan accordingly.
FAQ
Q: If DNS doesn't propagate, why does it seem like changes spread geographically?
A: It's coincidence, not physics. Resolvers with shorter TTLs or faster cache eviction update earlier. The order appears geographic only because popular public resolvers like Google (8.8.8.8) and Cloudflare (1.1.1.1) have similar configurations. Run multiple queries and you'll see the randomness.
Q: Does this mean I can ignore TTL and set it to 0?
A: Not exactly. A TTL of 0 is fine for testing but kills caching entirely, increasing resolver load and slowing the web. Best practice: lower TTL before a planned change, then raise it after propagation. But remember: 'propagation' is just waiting for old caches to expire. Lower TTL reduces that window.
Q: Isn't DNSGlobe just a pretty version of existing web tools?
A: Yes and no. Web tools like whatsmydns.net do the same query across resolvers. But DNSGlobe runs in your terminal, updates in real time, and most importantly – its visual map makes the non-linear behavior impossible to ignore. The experience changes how you think about DNS. That alone justifies its existence.