1. Confirm authority
Review nameserver delegation and identify the account managing the active zone. A registrar's DNS screen may contain unused historical records. Export or record the authoritative zone and keep it as the reference for the move.
2. Inventory required records
Include website records, mail routing, authentication, service discovery, verification records, and delegated subdomains where relevant. Compare automated imports with the authoritative source. Identify provider-specific features that do not translate directly into ordinary records.
3. Prepare the destination
Create the intended zone and compare it with the approved record set. Check important answers against destination nameservers where possible before changing delegation. Identify who can correct issues and who approves the cutover.
4. Review caching and DNSSEC
TTL affects how long answers can remain cached. Lowering a value does not immediately remove answers cached under the old value. Where DNSSEC is enabled, coordinate signing and delegation changes using the applicable registrar and provider procedures.
5. Define cutover and rollback
Record the window, responsible people, expected results, and conditions for pausing. Keep old services available during an appropriate transition. Rollback can also be affected by caching, so define practical validation rather than expecting every resolver to switch instantly.
6. Validate real services
Check authoritative answers, web access, certificates, mail behavior, and relevant business integrations. Record final nameservers, the active management account, and follow-up work. Retire old configuration only after transition checks and the agreed retention period.
A useful starting point
Check the destination before changing delegation, then validate the services people actually use.