Using the Enterramon DNS Tool

DNS propagation

DNS propagation isn’t instant and it isn’t uniform. Every resolver caches records for however long the TTL says to. Check DNS from your own laptop and you’re seeing one resolver’s cache, 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. A single resolver can return stale or inconsistent results that have nothing to do with your DNS change. Check only one and there’s no way to tell a real propagation delay from a resolver that’s just being slow. Run all five regions and that’s twenty lookups total, and they all fire at once instead of one after another.

Reading the results

A single region gives you a plain table, one row per resolver, query time, TTL, the answers returned, status.

When all regions are selected, the tool highlights whether the resolvers agree and shows any outliers. Every resolver across every region agreeing on the same answer means propagation’s complete. The detail table’s underneath if you want to verify it yourself. Check it every so often, 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 gives you a rough sense of how long cached results are likely to persist. Whichever resolver’s still serving the old answer will drop it once its cache expires, and that’s how long the stragglers have left before they clear.

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. Some visitors still hit the old server, mail delivery becomes inconsistent, or verification checks fail without an obvious error, and your own machine shows everything working fine the whole time, because your resolver already picked up the new answer days ago.

Once the DNS tool shows full consensus, the Server Check is the natural next step to confirm the new server’s actually answering the way you’d expect.