NS Record Propagation CheckerVerify nameserver changes have reached every independent global DNS resolver
- 7 independent networks
- Records + DNS flags
- No ads, no sign-up
Independent networks
7 public DNS networks, queried in parallel
Every test query is answered by these unaffiliated resolvers on separate networks and infrastructure. When they agree, you can trust the result.
- 8.8.8.8
Google Public DNS
Google LLC · North America
- 1.1.1.1
Cloudflare
Cloudflare, Inc. · Global Anycast
- 94.140.14.14
AdGuard DNS
AdGuard Software Ltd. · Europe
- 45.90.28.0
NextDNS
NextDNS, Inc. · Global Anycast
- 185.222.222.222
DNS.SB
xTom / Layer0 · Europe
- 223.5.5.5
Alibaba DNS
Alibaba Cloud · Asia
- 119.29.29.29
DNSPod
Tencent Cloud · Asia
How it works
A test query for flag propagation check, done right
Most checkers query a single resolver or a set of geographically labelled servers behind the same anycast network. isPropagated queries genuinely independent DNS operators and compares both their records and their response flags.
Enter a domain and run the test query
Type any domain, pick a record type (A, AAAA, CNAME, MX, TXT, NS and more), then run a single test query that fans out to every network at once.
We query independent global networks
Instead of asking one resolver, we ask several unaffiliated public DNS networks in parallel — across North America, Europe and Asia — so no single cache can mislead you.
Compare records and DNS flags
Each network returns its answer plus the DNS response flags (AD, CD, RA, RD, TC). We check that both the records and the flags agree before calling a domain propagated.
Read the propagation verdict
A clear consensus score shows how many networks resolved the record and whether their answers match — so you know the moment a change is live everywhere.
What are NS records and why is nameserver propagation different?
NS (Nameserver) records delegate authority for a DNS zone to one or more nameservers. When you change your DNS provider — moving from GoDaddy's nameservers to Cloudflare, Route 53, or any other host — you update the NS records at your registrar. Those NS records tell the rest of the internet which servers hold the authoritative copy of your DNS zone.
Nameserver propagation is unique because it involves two separate systems: the registrar (where you change the NS values) and the root DNS infrastructure (TLD servers like .com, .net that distribute NS records to the world). This is why "nameserver propagation" is often cited as taking up to 48 hours — TLD servers refresh their NS delegations on their own schedule, typically within minutes but sometimes longer.
Until the new NS records are live everywhere, some resolvers will continue asking your old nameservers for DNS answers. If you moved all your zone records to the new provider without keeping the old nameservers active, those resolvers will receive errors or stale data. Always keep both old and new nameservers live until NS propagation is fully confirmed.
How to interpret NS propagation results
Each result card shows the nameservers the resolver currently sees for your domain. When all 7 resolvers return the same set of NS records pointing to your new DNS provider, delegation is complete. If some still show the old nameservers, those resolvers have not yet received the updated delegation from the TLD.
Note that NS records at the zone apex work differently from the NS records stored in your DNS zone — the registrar's NS records (glue records) take precedence. This checker queries the NS records as returned by each resolver, which reflects the TLD delegation state.
FAQ
Common questions about ns record propagation checker
How long does nameserver propagation take?
Nameserver changes propagate faster than their reputation suggests. The TLD servers (.com, .net, etc.) typically update within 30 minutes of a registrar submitting the change. The 24–48 hour figure is a legacy worst-case. In practice, most NS record changes are fully propagated within 2–4 hours.
Should I wait for NS propagation before making DNS record changes?
Yes. Add all your DNS records to the new provider first, then change the nameservers at the registrar, then confirm NS propagation. This order ensures there is no window where the new nameservers are live but your records are missing.
Why do different resolvers show different nameservers for my domain?
Each resolver caches the NS delegation it received from the TLD for the duration of the NS record TTL (usually 86400 seconds / 24 hours). Until each resolver's cache expires and re-queries the TLD, it will return the old nameservers. This is normal during a transition and not a sign of an error.
What happens to my DNS records during nameserver propagation?
Resolvers that still point to the old nameservers will continue serving records from the old zone. Resolvers that have switched to the new nameservers will serve records from the new zone. This is why both zones must have identical records during the propagation window.