Using the Enterramon DNS Tool
What is DNS
DNS propagation isn’t instant and it isn’t uniform. Every resolver caches records for however long the TTL says to, so it’s completely normal for Google’s resolver to already have your new value while OpenDNS is still handing out the old one. The real question after a DNS change was never “has it propagated,” it’s “how much of the internet has it propagated to,” and one lookup from your own laptop can’t answer that. All it tells you is what your ISP’s resolver currently thinks, one data point out of thousands.
Go to enterramon.com/dns-tool, enter a domain, pick a record type, A, AAAA, MX, TXT, NS, CNAME, or SOA. Leave it on All Regions for the full picture, or narrow it to one of the five if you’re chasing something specific to a part of the world.
Each region queries four public resolvers, Cloudflare, Google, Quad9, and OpenDNS. Run all five regions and that’s twenty lookups total. They fire in parallel rather than one after another, which matters more than it sounds like it should, twenty sequential DNS queries would have you sitting there for a while waiting on the slowest one before you see anything at all.
Reading the results
A single region gives you a plain table, one row per resolver, query time, TTL, the answers returned, status.
Run all regions and the consensus badge at the top does most of the work for you. Every resolver across every region agreeing on the same answer means you’re done, propagation’s complete. If they don’t agree, the same view points at exactly which resolver is behind rather than making you scroll through twenty rows to find it yourself. The detail table’s right there underneath if you want to verify it. That’s worth doing occasionally, because a resolver can sit out of step for reasons that have nothing to do with propagation, an outage on their end, a cache entry that hung around longer than it should have.
The lowest TTL figure next to the consensus badge is roughly your countdown. Whichever resolver’s still serving the old answer will drop it once its cache expires, so that number is about how long the stragglers have left before they sort themselves out without you needing to do anything.
Why it’s worth running
Most people reach for this right after making a change. Pointing a domain at a new server, switching CDN providers, updating an MX record for a new mail host, adding a TXT record for SPF or DMARC. Get any of that wrong and the symptoms are usually confusing rather than obvious, some visitors land on the old server, some mail bounces, some verification checks fail quietly, and your own machine shows everything working fine the whole time because your resolver already picked up the new answer days ago.
Worth mentioning, the reason we query four resolvers per region instead of one is exactly this kind of thing, a single resolver can be having a bad day for reasons that have nothing to do with your DNS change, and if you only checked one you’d have no way to tell a real propagation delay apart from Quad9 just being slow that afternoon. Comparing several side by side is what actually makes the consensus reading trustworthy rather than a coin flip.
