Domain & DNS

DNS-propagatie-controle

Controleer recordstatus op 15 DNS-servers wereldwijd.

Domain & record type We query 15 public resolvers in parallel and stream answers as they arrive.

Try: example.com google.com github.com

Over deze tool

After you change a DNS record, it does not take effect globally at once. Every recursive resolver caches answers for the TTL published by the authoritative nameserver, so different networks see old and new values for some time. This tool queries 15 public resolvers around the world in parallel and streams their answers to your browser as they arrive.

We cover the major anycast networks (Google, Cloudflare, Quad9, OpenDNS, NextDNS), privacy-focused providers (AdGuard, Mullvad, CleanBrowsing), regional resolvers (CZ.NIC in Europe, Yandex and Comss in CIS, Alibaba and DNSPod in Asia, Canadian Shield in CA, DNS.SB in DE). If a specific region or provider is still serving the old record, the table will show it.

When to use this tool

After changing nameservers or an A/AAAA record — confirm the new value is live everywhere before cutting traffic.
Investigating user reports that "your site does not load" — ask which resolver they use, and check that one specifically.
Tracking MX changes — mail servers retry with different resolvers, so a partial roll-out can cause silent delivery failures.
Detecting split DNS — if an AS routes a provider via GeoDNS, different regions get different answers; the country column highlights it.

How to read the results

Each row is one recursive resolver. OK means the resolver returned an answer (values shown); Timeout means no response in 5s (upstream is sluggish or blocked); Error means the resolver refused or returned a malformed reply. The time column is round-trip from our server — it depends on our location, not yours, so treat absolute numbers as "upper bound". What matters is consistency of the values across rows.

Veelgestelde vragen

Why do some resolvers still show the old value?

Because they cached it. The authoritative nameserver publishes a TTL (time-to-live) for every record; a recursive resolver may hold a copy for that many seconds before re-fetching. Common TTLs are 300s–86400s. If you lowered the TTL before the change, caches will clear faster; if not, expect up to one TTL worth of lag. Cloudflare and Google Public DNS sometimes pre-fetch records, but smaller resolvers always wait.

Why are a few resolvers marked Timeout?

Either the resolver is overloaded (happens briefly with smaller providers), blocked from our server's IP range, or just slow on that day. A single timeout does not mean your record is broken — look at the other 14 rows. If more than half time out simultaneously, re-run the check in a minute; if it persists, the problem is on our side.

How is this different from DNS Lookup?

DNS Lookup queries one resolver you choose and shows all record types at once. DNS Propagation queries many resolvers in parallel but only for one record type — it answers the question "is the new value visible everywhere?", not "what records does this domain have?". Use both together after a change: Lookup to verify the authoritative value, Propagation to watch it spread.

Do you check IPv6-only resolvers?

Not in the current list. All 15 resolvers are queried over IPv4 at UDP port 53. IPv6 visibility across the public DNS landscape is very uneven; we will add IPv6 rows once enough providers commit to stable IPv6 anycast.

Can I check records other than A and AAAA?

Yes — pick MX, TXT, or NS from the dropdown. For more exotic types (CAA, SRV, SOA, CNAME, PTR), use the DNS Lookup tool — propagation checks are most useful for record types that client networks rely on (host addresses, mail routing, TXT verification, nameserver delegation).