DNS & technology

Change nameservers: prepare the DNS zone first

Change nameservers with a checklist covering website, email, DNSSEC and verification after the switch.

Reviewed and updated:

Change nameservers: prepare the DNS zone first: overview showing Copy old zone, Test new zone, Change delegation

Changing nameservers changes where authoritative DNS answers come from. It does not move website files or mailbox contents.

Copy more than the website record

Inventory website, mail, verification and subdomain records. Automatic imports may miss entries, so compare the new zone with the old before changing delegation.

Check DNSSEC before switching

DNSSEC delegation must match the new provider’s keys. A stale DS record can break validation. Coordinate this separately; a nameserver update does not imply automatic DNSSEC-key migration.

Change nameservers: prepare the DNS zone first: workflow showing Copy old zone, Test new zone, Change delegation
Copy old zone → Test new zone → Change delegation. Illustration: nlnamen.nl editorial team.

Test authoritative answers and caches

Use at least two valid, distinct nameservers and follow extension-specific requirements. Verify delegation and services after saving, and retain the old zone during the planned transition.

Your practical checklist

  • Copy the full zone.
  • Check DNSSEC and DS records.
  • Use at least two nameservers.
  • Test mail in both directions.
In practice
A new zone can serve the website correctly while missing MX records prevents mail delivery.

Sources and further reading

Registration rules and provider functions can change. Check the current requirements for your domain before ordering or changing services.