Edge
Migrating from Partial CNAME to Managed CNAME
Allow access to the /.well-known path when Shield is enabled.
Update external DNS records to route traffic directly to Acquia Edge Managed CNAME.
Important: A migration from a full authoritative setup on Cloudflare requires that you transfer authoritative DNS hosting to a third-party DNS provider (such as Route 53, NS1, or GoDaddy). Acquia and Cloudflare do not host your authoritative zone files after this migration.
Acquia Professional Services completes the following tasks before and during migration:
Security audit and threat assessment
Zone build and configuration
WAF rule deployment
Origin server configuration and health checks
Cache rules and page rules
Rate limiting and bot management, if applicable
Go-live validation
Before you begin, verify the following:
You have access to your domain DNS provider (such as Route 53, Cloudflare, or GoDaddy).
You have access to Acquia Edge powered by Cloudflare at dash.cloudflare.com.
You have received your [name].acquiaedge.net CNAME target.
Before you proceed, determine which legacy DNS configuration your organization currently uses with Acquia Edge:
Option A (Partial CNAME): A third-party provider hosts your domain authoritative DNS. You route traffic to Acquia with CNAME records. This path requires only an update to your existing CNAME target value. This path requires no changes to your nameservers.
Option B (Full Authoritative DNS): Acquia Edge and Cloudflare act as your primary authoritative DNS provider. Cloudflare hosts your full zone file. This path requires you to transfer authoritative DNS management to a third-party provider, recreate your zone records, and update nameservers at your registrar.
If your domain uses a Partial CNAME setup, the migration is lightweight. It does not require changes to your authoritative nameservers.
Acquia Professional Services provides a list of hostnames scheduled for migration to the Managed CNAME configuration.
Review the list of hostnames.
Add notes for any discrepancies.
Identify any legacy domains to remove.
Specify the preferred launch order for hostnames.
Acquia Professional Services provides documentation that shows which rules transfer to the Managed CNAME configuration. This document shows how rules consolidate to streamline rule management.
Review the documented rules.
Add notes for any discrepancies or concerns related to rule transfers.
Acquia Professional Services adjusts the rules based on your feedback.
Acquia Professional Services builds origin DNS routing from your existing DNS configurations. This process configures a default origin server and custom origin servers from your current DNS data.
Acquia Professional Services adds the verified hostnames to the Managed CNAME configuration as custom hostnames in your preferred launch order. Acquia Professional Services adds hostnames immediately before launch to ensure timely HTTP validation.
Acquia Professional Services updates the legacy zone DNS to route traffic to the Managed CNAME configuration. This routes traffic through the newly migrated rules.
Update legacy DNS to route traffic to the new [name].acquiaedge.net configuration.
Verify that SSL and hostnames are active.
Verify that the site renders without SSL or origin errors.
Confirm that the site launch is successful.
Acquia Professional Services completes the hostname launches for Step 3 and Step 4 based on the order of preference defined in Step 1.
Acquia Professional Services provides a final document with required DNS changes. Complete these DNS changes with your primary DNS provider:
Lower the DNS TTL to 5 minutes or less.
Wait for the DNS TTL change to propagate.
Update primary DNS records based on the details from Professional Services.
Verify that DNS has propagated.
Acquia Professional Services removes the legacy zone configurations. After cleanup, only the [name].acquiaedge.net zone remains available in the account.
For applications that use a full authoritative DNS configuration, complete Steps 1 through 5 in Option A, and then complete the following steps:
Acquia Professional Services provides a final document with required DNS changes. Complete these DNS changes with your primary DNS provider:
Export DNS records from Cloudflare with the Cloudflare user interface or the Cloudflare API.
Lower the DNS TTL to 5 minutes or less.
Wait for the DNS TTL change to propagate.
Import your DNS records into a third-party DNS provider using the exported configuration.
Update primary DNS records based on the details from Professional Services.
Verify that DNS has propagated.
Acquia Professional Services removes the legacy zone configurations. After cleanup, only the [name].acquiaedge.net zone remains available in the account.
TTL management: If you lowered DNS TTL values before migration, reset them to standard values (for example, 3600 seconds) after traffic is fully stable.
Deprovisioning requests: Confirm with Acquia Support that all legacy Cloudflare zones or old IP configurations from your previous setup are scheduled for deprovisioning.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Edge