Updating Private Nameserver IP Addresses Without Breaking DNS
If you’re migrating your DNS infrastructure to a new server, your private nameservers’ underlying IP addresses need to change — do this in the wrong order and every domain relying on them can go offline simultaneously.
Why the order matters
Every domain using your private nameservers depends on ns1.yourdomain.com/ns2.yourdomain.com resolving to a server that’s actually answering DNS queries correctly. If you point the glue record at a new IP before that new server is fully configured and answering for every domain it needs to serve, every one of those domains starts failing to resolve at the exact same moment.
The safe update sequence
- Set up the new DNS server first, fully configured with every zone/domain your nameservers currently serve, running in parallel with the old one.
- Verify the new server directly — query it explicitly (e.g.
dig @new-server-ip yourdomain.com) to confirm it answers correctly for every domain, before it’s live in any public nameserver record. - Update the glue record at the registry to point the nameserver hostname at the new IP.
- Wait for propagation before decommissioning the old server — glue record changes follow the same propagation timing as any DNS change, and some resolvers may cache the old IP for a while.
- Keep the old server running until you’re confident (via monitoring, or simply waiting a generous multi-day window) that traffic has fully shifted to the new one.
A staged alternative for extra safety
If your setup allows it, temporarily running both old and new DNS servers with identical zone data — rather than an instant cutover — means even resolvers still caching the old IP get correct answers throughout the transition, since both servers are answering correctly during the overlap window.
The core principle
Never point a glue record at a server until you’ve independently verified that server is already answering correctly for everything it needs to serve — the glue record update should be the last step, not an early one.
Our support team is here 24/7
Open a ticket or send us a message -- a real person replies to every request.
Contact support