Hostnames
0 hostnamesAdd every hostname going live in this cutover. Each one pairs 1:1 with the edge hostname it will CNAME to.
Pasting into the box fills the rows automatically. An edge hostname is paired with its hostname whether it sits on the same line or a few lines below it — so a copy of the Control Center Property Hostnames table works as-is. Surrounding text, numbering, table pipes,
IN CNAME and status text such as Multiple certificates / Manage in CPS / Validated are ignored.
Go-live status
ActivatedWe have activated the configuration on Akamai production. The property is ready — the only remaining step is updating DNS so live traffic routes through the Akamai edge network.
1. Point DNS to Akamai
DNSUpdate the DNS record for each hostname below to CNAME to its Akamai edge hostname. This is the change that actually routes live traffic onto Akamai.
Note
Only the record shown below changes. Leave every other DNS record for the hostname (MX, TXT, etc.) untouched.
2. Propagation timeline
TimingThe switchover depends entirely on the TTL (Time to Live) of the existing DNS record.
Tip
To accelerate the transition, lower the DNS TTL a few days before the migration, perform the CNAME switch, then revert the TTL back to its standard value once cutover is confirmed stable.
3. Troubleshooting & rollback
If something looks wrongIf application issues, performance drops, or errors occur immediately after changing DNS:
- Roll back immediately. Revert the DNS CNAME record back to the original configuration (pointing directly at the origin server).
- Investigate safely. Report the specific issue directly to Akamai support so it can be debugged in an isolated environment without affecting live production users.
Rollback first
Don't debug in place on live traffic — revert the CNAME, confirm the site is healthy again, then investigate.