Offer

Pay yearly and get 2 months free + an extra 30% off your hosting

Claim offer
HostingWeb HostingLiteSpeed and NVMe on FlyPanelfrom ৳100BDIX HostingPeered inside Bangladeshfrom ৳100WordPress HostingTuned for WooCommercefrom ৳1,000
Built in-houseFlyPanel, malware protection, backupsCustom-tailored, included on every plan→
2 months free on yearlyCompare products
ServersVPS HostingKVM with full root accessfrom $20BDIX VPSPeered inside Bangladeshfrom $20Dedicated ServersAMD Ryzen and dual Xeonfrom $250
1 Gbps port, Tier-3 datacentersCustom build
ResourcesKnowledgebaseSetup guides and troubleshootingBlogProduct news and performance tipsAbout Doze HostWho we are and where servers liveNetwork statusLive uptime for every service↗
Register a domainSearch and register a new nameClient areaBilling, services and invoices↗
Talk to an engineer, 24/701795 470074
Talk to us, 24/7Call an engineerReal people, day and night01795 470074Email supportsupport@dozehost.com↗Open a ticket27 min average first response↗
Help yourselfKnowledgebaseSetup guides and troubleshootingBlogProduct news and performance tipsNetwork statusLive uptime for every serviceLive
Client area: billing, services, invoicesLog in
Hosting Web Hosting ৳100/moLiteSpeed, FlyPanel, daily backups BDIX Hosting ৳100/moPeered inside Bangladesh WordPress Hosting ৳1,000/moTuned for WooCommerce
Servers VPS Hosting $20/moKVM with full root BDIX VPS $20/moPeered inside Bangladesh Dedicated Servers $250/moAMD Ryzen and dual Xeon
Domains
Resources Knowledgebase Blog About Doze Host Network status
Help Call 01795 470074Real engineers, 24/7 Email supportsupport@dozehost.com Open a ticket27 min average first response Knowledgebase Blog
Get started Log in
Home / Knowledgebase / DomainsDomains

Updating Private Nameserver IP Addresses Without Breaking DNS

Last updated July 21, 2026About 2 minutes to read

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

  1. Set up the new DNS server first, fully configured with every zone/domain your nameservers currently serve, running in parallel with the old one.
  2. 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.
  3. Update the glue record at the registry to point the nameserver hostname at the new IP.
  4. 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.
  5. 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.

Still stuck?Our support team is here 24/7. A real person replies to every request.