Domain cutover

A domain cutover changes where public DNS sends requests.

Prepare the Easel deployment and rollback path before changing traffic.

Before the cutover

Confirm:

• Production validation is complete
• The expected Easel Production deployment is Ready and Current
• The previous platform remains available
• Existing DNS values are recorded
• Relevant TTLs were lowered in advance
• The domain is added in Easel
• Mail and verification records are preserved
• Monitoring is active
• Rollback criteria are agreed

See Migrate a domain to Easel for detailed DNS guidance.

Define rollback criteria

Examples include:

• Sustained 5xx rate above an agreed threshold
• Authentication unavailable
• Database writes failing
• Critical webhook failures
• TLS errors
• Severe latency regression

Use application-specific criteria rather than relying only on total request volume.

Change DNS

Update the record to the exact value shown by Easel:

Do not use ALIAS, ANAME, or CNAME flattening for apex verification. Do not add AAAA unless Easel shows IPv6 values for your project.

Do not remove unrelated records such as MX, SPF, DKIM, DMARC, or service verification TXT records.

If you use Cloudflare or another proxy, switch to DNS-only until the domain is live on Easel. See DNS configuration.

TLS

Easel provisions certificates with Let’s Encrypt after DNS points at Easel. First HTTPS requests can fail until the certificate is Ready. See TLS.

Verify from multiple networks

Check:

dig example.com A
dig www.example.com CNAME
curl -I https://example.com

Confirm:

• DNS reaches Easel
• HTTPS certificate is valid
• Correct project responds
• Expected deployment is Current
• Canonical redirect works

Monitor the application

Watch in Observability and Logs:

• Request volume and status codes
• Error rate and latency
• Function failures
• Authentication and API writes
• Cache behavior
• Traffic still reaching the old platform

Keep the previous platform active

Do not immediately remove the old domain configuration, delete the project, or revoke credentials.

Clients may retain cached DNS answers during the transition.

Raise TTL after stabilization

Once traffic is stable and rollback is no longer likely, increase the DNS TTL to the desired operational value.

Related guides

• Migrate a domain
• Migration rollback
• Instant Rollback