Website migration with SCDN: checks before and after DNS cutover
Validate origin access and certificates before staged cutover, with explicit rollback and cache handling.
Contents of this article
Separate configuration from traffic cutover
Inventory domains, origin addresses, HTTPS, request sizes and special protocols. Verify Host handling and certificates before changing production DNS. Avoid combining application, database and entry-point migrations in one change.
DNS changes do not move existing connections
Clients and resolvers may retain older answers, and persistent connections may keep their existing path. Provide a controlled overlap period and do not immediately shut down an origin still receiving legitimate traffic.
Rollback must preserve data consistency
Rollback involves more than restoring DNS if orders, uploads or account state changed during migration. Confirm data consistency between environments and retain versioned assets and compatible authentication rules.
Observe critical actions after cutover
Retest sign-in, uploads, downloads, callbacks and persistent sessions from key regions. Record errors and origin load, then narrow access to retired entry points once the change is verified.