Why Does Nameserver Change Take 24-72 Hours?
The real reason NS changes propagate slowly and the caching structure at each level
You changed nameservers from onamae.com to Cloudflare — why doesn't it take effect immediately? An A record change finishes in minutes to hours, so why do nameserver (NS) changes take 24-72 hours? This article explains how NS changes propagate through the DNS hierarchy, why cache TTLs at each level are so long, and practical tips for faster migration.
How It Works
Request NS change to new nameserver (e.g., Cloudflare) at registrar (onamae.com, etc.)
Registrar notifies TLD registry (Verisign, etc.) of the change via EPP protocol
Registry updates .com zone file (minutes to hours)
Wait for worldwide ISP resolver caches to expire (TLD NS TTL: 48 hours)
After cache expiry, resolver re-queries TLD → gets new NS → new NS responds with A/CNAME records
Pros
- ✓ NS change itself is simple to perform from registrar dashboard
- ✓ Zero downtime during transition if identical records are set on both NS
- ✓ Propagation status can be verified in real-time with dig +trace and whatsmydns.net
- ✓ Public DNS (Google, Cloudflare) offer cache purge functionality
Cons
- ✗ TLD NS record TTL (48 hours) cannot be controlled by domain owner
- ✗ Cannot force-flush caches on all ISP resolvers worldwide
- ✗ Some ISPs ignore TTL and enforce their own minimum cache time (can delay up to 72 hours)
- ✗ Exact propagation completion time is unpredictable — varies per user due to different ISPs