A controlled DNS cutover changes where a domain resolves while preserving records that keep the website and other services working.
Plan the CMS Max launch around authoritative DNS access, exact assigned records, TTLs, email preservation, certificate readiness, verification, and rollback.
Before changing DNS
- Identify the authoritative DNS provider and an authorized person who can make changes.
- Export or record existing A, AAAA, CNAME, MX, TXT, CAA, and other service records.
- Obtain the exact CMS Max target and verification instructions for this domain.
- Plan TTL changes with the DNS owner; caches can continue using older answers until their TTL expires.
- Confirm how the apex domain, www host, redirects, email, and third-party services should behave.
Launch and verify
- 01Apply only the approved record changes. Preserve mail and verification records unless their owners approve a change.
- 02Check authoritative answers. Verify the intended records at the DNS provider and through independent resolvers.
- 03Test the whole service. Check apex and www over HTTPS, forms, checkout, email, redirects, and important integrations.
- 04Monitor through the TTL window. Different resolvers can show old and new answers during a cutover.