Check DNS record propagation across global resolvers

DNS propagation and resolver cache checks

Use this DNS propagation checker after changing A, AAAA, MX, TXT, CNAME, or NS records. It compares answers from resolvers so you can see whether caches still return old data.

When to use this tool

  • After moving a website to a new IP address.
  • After changing mail provider MX records.
  • After publishing SPF, DKIM, DMARC, or verification TXT records.
  • When users in different networks see different DNS answers.

How to read the results

  • Matching answers usually mean propagation is consistent.
  • Mixed results often mean resolver caches are expiring at different times.
  • No answer may indicate missing records or wrong nameservers.
  • TTL helps estimate how long old values can remain cached.

Common propagation issues

Stale cache: a resolver still serves the previous record until TTL expires.
ISP resolver delay: provider resolvers may update slower than public resolvers.
Mixed results: expected during rollout, but check nameservers if it persists.
Nameserver mismatch: edits may be made at a DNS provider that is no longer authoritative.

Many changes appear within minutes, but cached records can remain until their TTL expires. Some networks may show old answers for several hours.

TTL is the number of seconds a resolver may cache a DNS answer. Lower TTL values usually make planned changes easier to roll out.

Resolvers cache records independently. Some may have refreshed the new value while others still hold the old cached answer.

Flush the local OS or browser DNS cache, restart the resolver service if you control it, or query a different public resolver to compare results.