Before cutover, preserve records that are not moving
Before changing website routing, inventory the existing DNS records and identify which services use them. Mail routing and sender authentication can depend on records unrelated to the public web server. A website migration does not automatically authorize moving email. Keep the intended change explicit: which hostname will point to which destination, which records remain untouched and who has authority to make that change.
Check the receiving website first
Use the supported preview or testing route to confirm the destination application is ready before directing readers to it. Check the intended hostname configuration and HTTPS requirements using current provider instructions. Do not guess an IP address or copy a value from a different server. The migration record should contain the exact source and destination identifiers, but it should not expose private credentials or unrelated account information.
Plan for a period of mixed observations
Different clients can observe DNS changes at different times, so a single successful load is not proof that every visitor has moved. Plan how the old and new applications handle writes during the transition. A fictional store cannot safely assume that orders stop arriving at the old environment the moment a record is edited. Keep the data-timing and recovery plan linked to the cutover rather than treating DNS as an isolated technical checkbox.
Verify web and mail paths separately
After the change, check the canonical website, any supported alternate hostname and the relevant business paths. Confirm authorized test messages reach the intended mailbox without contacting customers. A working homepage is not evidence that email authentication or routing stayed correct. Preserve the old configuration record and stop broad changes if results are uncertain. Do not make repeated unrelated DNS edits in the hope that one of them resolves an unexplained symptom.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Cloudways sender-domain and email DNS setup — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
- Cloudways custom-certificate deployment — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21