Features

Website Domain Handover: DNS Cutover, Email and Acceptance Checklist

Plan a business website domain handover: verify registrar access, DNS records and email dependencies, then test cutover, rollback, bilingual pages and enquiry d

Before changing the supplier of a business website, confirm the domain registrant, registrar account, DNS management account and renewal owner. Then decide whether the DNS service also needs to move. A hosting move may require changes to verified website records within the existing DNS service. A DNS provider move requires carrying over email, verification and other service records first. Accept the handover through public website checks, business email tests and enquiry records. This guide assigns practical tasks to business owners, content staff and operations teams.

1. Separate four domain handover actions

A request to “hand over the domain” can describe several jobs. Record the current state, target state, operator and reviewer for each: a registrant change, registrar or account transfer, DNS service migration, and website destination change. A project may involve just one of them.

Alibaba Cloud’s domain transfer guide distinguishes registrar transfers, account transfers and registrant changes. Check the actual provider and domain type for applicable requirements, timing and confirmation steps. A supplier can provide controlled project access while the business retains its recovery channels and renewal owner.

  • Registrant: reconcile registration details with business authorization records and confirm the intended holder.
  • Registrar account: identify the organization managing the domain and the people responsible for renewals and recovery.
  • Authoritative DNS: identify the active nameservers, management account and owner of each zone.
  • Hosting and CDN: identify the deployed environment, certificates and application that ultimately serve visitors.

Deliver credentials, verification codes and transfer secrets through controlled channels. Ordinary project registers should record their custody location and authorized people. Sign off expiry dates, recovery addresses and backup arrangements for multifactor authentication together.

2. Inventory DNS records and find email dependencies

Operations staff should export and reconcile records from the active DNS platform, including routing policies, proxy settings, wildcards, delegated subdomains and provider-specific records. Automated scans can assist; the maintainer confirms completeness. The following register fields are examples. Fill them with actual environment values.

ServiceHandover evidenceBusiness reviewer
Apex and wwwA, AAAA or CNAME, destination, TTL, routing and proxy stateWebsite maintainer
Business emailMX priorities and targets, SPF, DKIM, DMARC and mail-host recordsEmail administrator
Downloads and languagesFile hosts, language subdomains, certificate coverage and application bindingsContent and operations owners
Verification and other servicesOwnership TXT, CAA, SRV, service subdomains and purposeRelevant system owner

For a hosting move, identify each website record requiring a change and retain email and other records according to their confirmed purposes. Check IPv6 destinations wherever AAAA records exist. With a CDN, reconcile both the DNS destination and origin configuration. Operations staff should handle DS records and the signing chain of DNSSEC-enabled zones under the provider’s migration procedure and retain validation evidence.

3. Verify the new website before the DNS window

Before changing public DNS, operations staff should test the new environment through a controlled method using the production Host: HTTPS, site bindings, both languages, attachments, administrative APIs and form processing. Content staff can use the website migration and handover checklist to check pages, old URLs and materials. See the staging isolation guide for data and notification separation.

  1. Define the scope: changing website records and migrating an entire DNS zone each need their own final change list.
  2. Preserve configuration: record previous and new values, TTLs, timestamps, operators, reviewers and rollback criteria in a controlled backup.
  3. Plan caching in advance: use existing TTLs to choose the lead time. After lowering a TTL, allow the previous cache lifetime to expire. Consider record caches, nameserver delegation caches and application/CDN caches separately.
  4. For DNS migration, configure and verify records at the destination before changing nameservers under the provider’s instructions. Keep the original service available through the agreed observation period and relevant cache windows.
  5. Agree observation and rollback duties: specify the rollback approver, restoration of previous destinations, and reconciliation of content and enquiries received by either environment during the transition.

Cloudflare’s migration preparation documentation highlights exports, comparison after import and email-record checks. Set actual TTLs and waiting windows for the environment. A local refresh demonstrates the current access path; acceptance should also cover other networks and resolution paths.

4. Example: move hosting and retain the email service

This is a fictional project. An equipment company uses example.com and www.example.com for Chinese and English product pages. Separate suppliers operate its email and website. The project moves the website to a new server while retaining the email service and current DNS account.

The project owner approves destination changes for two website entry records. Operations staff first verify Chinese pages, /en English pages, product PDFs and enquiries on the new environment, and check for AAAA records needing corresponding changes. The email administrator records the MX and sending-authentication values being retained. After cutover, reviewers open the website from two networks and exchange numbered test messages in both directions between business and external test mailboxes.

An authorized reviewer submits a clearly marked test enquiry and records its submission time, backend record ID and notification result. If the website works while email fails, the email administrator and operations staff investigate recorded differences. A rollback of website destinations also requires reconciliation of enquiries received at both environments during the cutover. Handle test materials under the project’s retention rules.

5. Sign off seven results

  1. Account control: an authorized business representative signs into the registrar and DNS console and checks project permissions, recovery channels, expiry alerts and backup staff.
  2. DNS consistency: technical staff compare authoritative responses with selected recursive resolvers and record time, network, record type and expected results. Keep an observation task open for remaining differences.
  3. Website entry points: check the apex, www, language and download hosts from different networks for HTTPS, redirects and the expected website.
  4. Bilingual SEO: check representative pages for HTTP status, title, description, canonical, language alternates and old URL destinations. Retain confirmed language and content paths when moving a website on its existing URLs.
  5. Email: the email administrator verifies the actual service and test messages in both directions, including authentication results in message headers where needed.
  6. Enquiries: reconcile the success message, backend record, notification and follow-up owner. See the enquiry form guide for notification troubleshooting.
  7. Ongoing maintenance: confirm monitoring owners, rollback records, observation exit criteria and future renewal owners. Use the HTTPS renewal checklist for certificate responsibilities.

Use six acceptance columns: entry point, expected value, actual result, evidence location, owner and recheck time. Record specific open actions and affected services for further work under the project change process.

6. What does CatchCMS handle?

CatchCMS manages domain bindings by site and supports site languages and their content. The current official website uses Chinese and English paths on one hostname. Check domains, languages and themes against each project’s actual configuration. Refer to multiple-site management and multilingual content management for configuration and scope.

Registrant and registrar transfers, authoritative DNS, email configuration, CDN services, TLS certificates, cache observation and external monitoring belong to project infrastructure and operations work, performed by people with the required access. Record CMS publication acceptance and infrastructure cutover acceptance separately. Prepare the domain list, site count, languages, deployment destination and maintenance responsibilities, then use the project enquiry page to confirm CatchCMS configuration and development scope.

7. Frequently asked questions

Does changing website suppliers require a registrar transfer?

Select account handover, registrar transfer, DNS migration and website destination changes individually for the project. Many hosting moves can use website-record changes within the existing DNS platform, subject to current access and service agreements.

Does a TTL of 300 seconds mean acceptance ends after five minutes?

Acceptance timing depends on previous caches, delegation records, different recursive resolution paths and application/CDN state. A 300-second TTL is one record setting. Close the task based on agreed business tests and observation results.

Is a working website sufficient to finish the handover?

Sign off business account access, the DNS register, email delivery, enquiry records and continuing maintenance responsibilities as well. Each owner supplies actual results for the business project owner to accept.