Document a DNS change for client approval

Direct answer

Do not treat a hostname change as proof that application data, email or certificates have moved.

Make DNS changes reviewable by naming the records, dependencies, owner and rollback point.

Illustrative example

Illustrative example: a client approves a new web target for a brochure site. The agency stores the previous record values, a scheduled window, the DNS owner and a test list for web and mail.

Work through the decision

1. Capture the current record set and identify which services depend on it.
2. State the requested record change, expected outcome and rollback record.
3. Name the person who can approve the change and who can edit the zone.
4. Verify the intended web path and unrelated mail path after propagation where relevant.

What this does not establish

DNS timing and third-party cache behaviour are not guaranteed by PrivateHostLab.