Changing your nameservers at the registrar is not the same kind of change as editing an A or CNAME record, and it propagates on a different clock. A nameserver (NS) change updates the delegation that lives in your parent zone, the top-level domain registry, and that delegation carries its own TTL set by the registry, commonly one to two days, not the TTL on records inside your own zone. So the right question is not just whether the world sees your new records yet, but whether the world sees that your domain is now delegated to the new nameservers at all. This guide shows how to read the parent delegation, query the authoritative and recursive layers separately, and confirm the new NS set is answering everywhere before you expect the rest of the zone to follow.
Why nameserver changes propagate differently
Ordinary records such as A, AAAA, and MX live inside your zone and are governed by the TTL you set on each one, often minutes to an hour. A nameserver delegation is different: it is stored one level up, in the parent zone run by the registry. When you point example.com at new nameservers, you are really asking the .com registry to change which NS records it hands out when a resolver asks who is authoritative for example.com. That delegation has a TTL chosen by the registry, and for most gTLDs it is 172800 seconds, which is 48 hours. Until that parent TTL expires at a given resolver, that resolver keeps sending queries to your old nameservers, no matter what you have changed inside the new zone.
This is why a nameserver move can feel slow and uneven while a plain record edit propagates in minutes. The delegation at the top controls everything beneath it, so nothing in the new zone matters to a resolver that has not yet picked up the new NS set.
Parent delegation versus child NS records
There are actually two copies of your NS records, and checking propagation means knowing the difference. The parent NS records are the delegation the registry publishes about your domain. The child NS records are the NS records configured inside your own zone, served by your nameservers themselves. In a healthy setup they match, but during a move they diverge for a while: the registry may still delegate to the old hosts while your new zone already lists the new ones.
| Signal | Parent (registry) NS | Child (in-zone) NS |
|---|---|---|
| Who publishes it | The TLD registry at the registrar's request | Your own authoritative nameservers |
| Controls resolution | Yes, this is the real delegation | No, it is informational |
| Governing TTL | The registry NS TTL, often 24 to 48 hours | The TTL you set inside the zone |
| Check it with | A query to a TLD server | A query to your own nameserver |
The delegation that matters is the parent copy, because that is what tells the rest of the internet where to send queries. If the parent still shows old nameservers, the move has not taken effect yet regardless of what your new zone says.
Read the parent delegation directly
To see what the registry is publishing, ask a TLD nameserver, not a recursive resolver. The cleanest way is a trace, which walks from the root down through the TLD to your domain and shows the delegation at each step:
$ dig example.com NS +trace
;; ... root servers ...
com. 172800 IN NS a.gtld-servers.net.
;; ... then the delegation for your domain ...
example.com. 172800 IN NS ns1.newhost.com.
example.com. 172800 IN NS ns2.newhost.com.
You can also query a TLD server for the delegation on its own. The answer comes back in the authority section because the registry is delegating rather than answering authoritatively:
$ dig example.com NS @a.gtld-servers.net
;; AUTHORITY SECTION:
example.com. 172800 IN NS ns1.newhost.com.
example.com. 172800 IN NS ns2.newhost.com.
When those lines show your new nameservers, the registry has published the change. The 172800 is the parent TTL, the maximum time a resolver can keep caching the old delegation. The registrar's WHOIS or RDAP record also lists the sponsoring nameservers, which is a quick sanity check that the registrar accepted your change in the first place.
Authoritative versus recursive answers
Once the parent delegates to the new hosts, confirm the new nameservers actually answer authoritatively. Query one of them directly and look for the aa (authoritative answer) flag in the header:
$ dig example.com NS @ns1.newhost.com
;; flags: qr aa rd; ...
;; ANSWER SECTION:
example.com. 3600 IN NS ns1.newhost.com.
example.com. 3600 IN NS ns2.newhost.com.
The aa flag means that server considers itself authoritative for the domain, which is what you want from the new hosts. Then query a public recursive resolver such as 8.8.8.8 or 1.1.1.1 to see what the caching layer is serving. If a recursive resolver still returns the old nameservers, it is holding a cached delegation that will expire within the remaining parent TTL. A resolver showing a TTL well below 172800 is counting down a cached copy rather than reading the registry fresh.
Check it worldwide, not just from your desk
Your own resolver is a single vantage point and may have cached the old delegation hours before your change. Because every recursive resolver caches independently, nameserver propagation is a patchwork: some regions pick up the new NS set within minutes while others keep the old one until their cached delegation expires. The only way to judge the global state is to query many resolvers across regions at once and compare. The Valla DNS propagation checker queries resolvers in multiple locations and shows which ones already return your new nameservers and which are still serving the old delegation, so you can see how far the change has spread before trusting it everywhere.
A checklist for a nameserver change
- Before the move, note the parent NS TTL (often 48 hours) so you know the worst-case wait.
- Build the full zone at the new DNS host first, so the new nameservers answer correctly the moment delegation points to them.
- Change the nameservers at your registrar, then confirm WHOIS or RDAP lists the new hosts.
- Query a TLD server to verify the parent delegation now shows the new nameservers.
- Query each new nameserver directly and confirm the
aaflag is set. - Run a worldwide propagation check and wait out the parent TTL before you retire the old host.
Frequently asked questions
How long do nameserver changes take to propagate?
Up to the parent NS TTL set by the registry, which for most gTLDs such as .com is 48 hours. Many resolvers update sooner, but any resolver that cached the old delegation can keep it until that TTL expires, so plan for the full window rather than an average.
How do I know if the registry has published my new nameservers?
Query a TLD server directly, for example dig example.com NS @a.gtld-servers.net, or run dig +trace. The authority section shows the delegation the registry is handing out. When it lists your new nameservers, the parent change is live.
Why does my new zone look correct but the site still uses the old server?
Resolvers are still following the old parent delegation, so they never query your new zone. Nothing inside the new zone takes effect until the delegation at the registry points to the new nameservers and the cached old delegation has expired.
What is the difference between parent and child NS records?
Parent NS records are the delegation the registry publishes and are what actually direct resolvers to your nameservers. Child NS records are the NS records inside your own zone. Resolution follows the parent copy; the child copy is informational and should match it.
Can I speed up nameserver propagation?
Not after the fact, because the old delegation TTL was already cached by resolvers. Unlike ordinary records, you cannot lower the registry NS TTL yourself, so the registry's value governs the worst case. The best you can do is prepare the new zone in advance so resolution is clean the instant delegation switches.
Moving nameservers now? Confirm the registry is delegating to the new hosts, then watch the new NS set roll out region by region with the Valla DNS propagation checker.