Update a CNAME when a custom-domain integration moves to a new canonical hostname, or remove it when that integration is retired. A forgotten alias to an unclaimed third-party service can create a domain-takeover risk.
IN THIS ARTICLE
Prepare for the change
Confirm the DNS zone is authoritative and record the old alias, target and TTL. Verify the new service has accepted your custom hostname before changing traffic. Plan any verification and HTTPS requirements with that service.
01 Change or remove a cPanel CNAME alias
- Open Zone Editor > Manage and filter for CNAME records. Select the exact alias hostname.
- To move it, choose Edit and replace only the target with the new complete hostname. Do not include a scheme, port or path.
- To retire it, use its delete action after confirming no website, mail client or verification process still needs the alias.
- Save and inspect the authoritative DNS response. Test the custom domain at the destination after cached answers have had time to expire.
- When leaving a third-party platform, remove or repoint the DNS alias before releasing the corresponding service resource where practical.
Confirm the expected result
The alias should resolve through the intended target, and the destination should serve your hostname with a valid certificate. For retirement, confirm the old alias no longer points to an abandoned resource.
What if the replacement CNAME target fails or conflicts with another record?
If the new target fails, restore the previous known-good value while retaining ownership of the old resource. If you need to replace a CNAME with an A or TXT record, resolve the same-name conflict deliberately rather than creating an invalid mixed record set.