Move hostnames between zones
As a SaaS provider, you may want, or have, multiple zones to manage hostnames. Each zone can have different configurations or origins, as well as correlate to varying products. You might shift custom hostnames between zones to enable or disable certain features. Cloudflare allows migration within the same account through the steps below:
CNAME
If your custom hostname uses a CNAME record, add the custom hostname to the new zone and update your DNS record to point to the new zone.
Add custom hostname to your new zone.
Direct your customer to change the DNS record so that it points to the new zone.
Confirm that the custom hostname has validated in the new zone.
Wait for the certificate to validate automatically through Cloudflare or validate it using Domain Control Validation (DCV).
Remove custom hostname from the old zone.
Once these steps are complete, the custom hostname’s traffic will route to the second SaaS zone and will use its configuration.
A record
Through Apex Proxying or BYOIP, you can migrate the custom hostname without action from your end customer.
Verify with the account team that your apex proxying IPs have been assigned to both SaaS zones.
Add custom hostname to the new zone.
Confirm that the custom hostname has validated in the new zone.
Wait for the certificate to validate automatically through Cloudflare or validate it using DCV.
Remove custom hostname from the old zone.
Wildcard certificate
If you are migrating custom hostnames that rely on a Wildcard certificate, Cloudflare cannot automatically complete Domain Control Validation (DCV).
Add custom hostname to the new zone.
Direct your customer to change the DNS record so that it points to the new zone.
Validate the certificate on the new zone through DCV.
The custom hostname can activate on the new zone even if the certificate is still active on the old zone. This ensures a valid certificate exists during migration. However, it is important to validate the certificate on the new zone as soon as possible.