2 min readAn original planning guide. Use the linked primary documentation for platform details and the supported procedure for your environment.
Identify the authoritative zone
Confirm where active records are managed and which exact name and type must change. Avoid editing a similarly named inactive zone.
Capture current state
Record the relevant existing values and TTLs in a controlled note. Identify website, email, and verification records that must remain intact.
Plan timing and validation
Account for existing caches. Choose checks for authoritative answers, recursive answers, and the actual affected service.
Define recovery and ownership
Record the previous values, the person applying the change, and the conditions for corrective action. Note that cache effects may outlast an edit.
Worked scenario
See the plan in practice.
Moving a website might require its address records while the business's MX and mail-authentication records remain with the email service.
Review your result
Your acceptance checklist
Name and type exact- Previous values retained
- Service test defined
Use these checks to identify gaps in your dns change record. Assign an owner to any unresolved item before the next dependent step.
The terms behind the task
Primary references
For the underlying concepts and current platform details:
