Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Domains & DNS

Domain nameserver migration: move DNS hosting without dropping records

Published August 2026 · 2 min read · Updated 2026-09-05

A nameserver migration changes who is authoritative for an entire DNS zone. That can affect websites, email, verification records, subdomains, APIs, and third-party services simultaneously, so the safe sequence is copy, compare, delegate, observe, and only then retire the old DNS service.

Inventory the current authoritative zone

Export or query A, AAAA, CNAME, MX, TXT, CAA, SRV, subdomain delegations, DKIM selectors, DMARC, SPF, verification tokens, and any wildcard records. Record TTLs and DNSSEC state.

Check for provider-specific synthetic records or flattening that may not copy literally.

Build the new zone before delegation

Create equivalent records at the new DNS provider and query its authoritative servers directly before the registrar nameserver change. Make sure mail and service-specific records were not omitted because they are invisible on the homepage.

If DNSSEC is active, coordinate DS/signing according to the old/new provider procedures.

Change delegation without deleting the source

Update nameservers at the registrar/registry and monitor parent delegation plus recursive answers. Keep the old zone serving the same data through the cache/registry transition.

Avoid changing website IPs at the same moment unless there is a strong reason; one change at a time is easier to validate.

Retire only after public convergence

Verify multiple resolvers, web, mail, subdomains, API endpoints, and certificate renewal paths. Remove the old zone only when it is no longer authoritative or receiving meaningful queries.

  • Export the complete zone.
  • Prebuild/test the new authority.
  • Coordinate DNSSEC.
  • Keep old DNS through the transition.

Next step

Copy the zone, compare authoritative answers, lower risk before delegation changes and keep the old DNS service available until the new nameservers are proven.

Explore DotMoose domains and DNS

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move