Last check
Waiting for lookup
[DNS propagation checker]
Check DNS propagation before customers notice.
Look up A, AAAA, CNAME, MX, NS, TXT, SOA, and CAA records across public DNS resolvers to see whether a domain change is visible outside your own machine.
[Resolver check]
Query public DNS from one screen.
Enter a domain and choose the record type you changed. MarionetteOps queries multiple DNS-over-HTTPS resolvers and shows their answers, TTLs, status, and response times.
Propagation is resolver cache refresh, not an instant global push
What this DNS propagation checker does
This free DNS propagation checker compares the answers returned by several public recursive DNS resolvers. It is useful after changing an A record, moving mail to a new MX host, adding a TXT verification value, updating nameservers, or checking whether a CAA or SOA record is visible. Instead of trusting only your laptop, browser, or office network, you can see whether independent resolvers are returning the value you expect.
The tool supports A and AAAA records for IP addresses, CNAME records for aliases, MX records for mail routing, NS records for nameservers, TXT records for SPF, DKIM, DMARC, and ownership verification, plus SOA and CAA records for zone authority and certificate authority rules.
How DNS propagation works
DNS changes do not spread as a single global event. When you edit a record at your DNS provider, the authoritative nameservers may update quickly, but recursive resolvers still cache the previous answer until its TTL expires. That is why one resolver can show the new A record while another still returns the old IP address.
For a smoother migration, lower the TTL well before the change, wait for the old TTL to age out, make the update, then use a DNS propagation checker to compare resolver answers. After the new value is stable, raise the TTL again so routine lookups remain efficient.
When to use a DNS checker
Use this checker before and after website launches, email migrations, status page CNAME setup, SSL verification, domain ownership verification, CDN cutovers, and nameserver moves. DNS mistakes often look like application downtime from a customer's perspective, so DNS visibility belongs next to uptime monitoring, certificate checks, and status page communication.
DNS propagation FAQ
What is DNS propagation?
DNS propagation is the period when recursive DNS resolvers are gradually refreshing cached records after you change a domain record at your DNS provider.
How long does DNS propagation take?
Many changes appear within minutes, but propagation can take hours when old records had long TTL values. In difficult cases, cached answers may persist for up to 24 to 48 hours.
Why do DNS resolvers show different answers?
Resolvers cache answers independently. One resolver may have refreshed the new record while another is still serving the old value until its TTL expires.
Which DNS record types can this checker test?
The checker supports common operational records: A, AAAA, CNAME, MX, NS, TXT, SOA, and CAA.
Keep watching after propagation finishes.
MarionetteOps monitors uptime paths, certificates, domains, and status pages so DNS or certificate drift does not quietly turn into customer-visible downtime.