Connecting a domain to a new hosting account is usually straightforward, but a rushed DNS change can interrupt a website, break subdomains, or stop business email from arriving. This guide provides a reusable DNS cutover checklist: choose between nameservers and individual records, inventory your current setup, lower TTLs, verify the new host, protect email, and keep a rollback plan ready.
Overview
When you point a domain to a new host, you are changing how DNS directs visitors and services. DNS does not move your website files, databases, mailboxes, or domain registration. It tells browsers, mail systems, and other services where those resources can be found.
Before changing anything, confirm three separate responsibilities:
- Domain registrar: The provider where the domain is registered and renewed.
- DNS provider: The service that publishes the domain's DNS records. This may be the registrar, the existing host, or a separate DNS platform.
- Hosting provider: The new server or platform that will deliver the website.
These services can be operated by different providers. You can connect a domain to hosting without transferring the domain registration, and you can move a website without changing the nameservers. For a refresher on record types, see DNS Records Explained: A Practical Guide to A, CNAME, MX, TXT, and Nameserver Changes.
Choose the least disruptive connection method
| Method | Use it when | Main consideration |
|---|---|---|
| Change nameservers | The new host should manage the entire DNS zone and has provided authoritative nameservers. | You must recreate every required record before or immediately after the change, especially MX, TXT, and verification records. |
| Change A and AAAA records | You want to keep DNS with the current provider and point only the website to the new server. | Leave email, verification, and unrelated records unchanged. Confirm whether IPv6 is supported before changing an AAAA record. |
| Change a CNAME record | The hosting platform gives you a hostname rather than a fixed IP address, commonly for a subdomain or platform-managed site. | Follow the platform's exact hostname and note that the root domain may require a separate A, ALIAS, or ANAME-style option. |
Provider labels vary. Look for instructions called “connect domain,” “custom domain,” “DNS records,” or “nameservers,” and use the values supplied in the new hosting account rather than copying values from an unrelated setup.
Checklist by scenario
Before the cutover: create an inventory
Record the current configuration before editing it. Save a screenshot or export of the DNS zone where possible, and keep the following template with the project notes:
- Domain and subdomains: ____________________
- Current DNS provider and registrar: ____________________
- New hosting provider and assigned destination: ____________________
- Current A, AAAA, and CNAME records: ____________________
- MX records and mail provider: ____________________
- SPF, DKIM, and DMARC TXT records: ____________________
- Other TXT records for search, payment, analytics, or SaaS verification: ____________________
- Nameservers and DNSSEC status, if used: ____________________
- Current TTL values: ____________________
Confirm that the new website is complete on the hosting account before the DNS change. Test it using the host's preview URL, temporary domain, local hosts-file test, or another method the provider supports. Take a backup of website files and databases; the Website Backup and Recovery Plan provides a reusable approach for this preparation.
If you are changing nameservers
- Ask the new host for its authoritative nameservers.
- Copy all existing records that must remain active into the new DNS zone. Include MX, SPF, DKIM, DMARC, subdomains, verification TXT records, and any special records used by applications.
- Check the new zone for the website's required A, AAAA, or CNAME values.
- Confirm that the new host's DNS zone is active and error-free.
- Change the nameservers at the registrar, not merely in the old hosting panel.
- Keep the old hosting account available until the new website and email have been verified.
Nameserver changes transfer control of the domain's DNS zone. They are convenient when the new provider should manage DNS, but they are broader than changing a single website record.
If you are changing A, AAAA, or CNAME records
- Leave the domain's nameservers unchanged.
- Replace the website's existing A record with the new IPv4 address, if supplied.
- Change the AAAA record only when the new host supplies a working IPv6 destination. An outdated AAAA record can send some visitors to the old or incorrect server even when the A record is correct.
- Use the supplied CNAME for a subdomain or platform connection where instructed.
- Do not delete MX, TXT, or unrelated records simply because the website is moving.
For a WordPress or full website migration
Complete the file and database migration before changing DNS. Check the site's configured domain, permalink behavior, redirects, forms, media, scheduled tasks, and administrator access on the new host. After the cutover, review the WordPress Website Migration Checklist and monitor for missing assets, redirect loops, or database errors.
What to double-check
TTL planning and propagation
TTL, or time to live, tells recursive DNS resolvers how long they may cache a record. Before a planned cutover, lower the relevant TTL at the current DNS provider and allow the previous value's caching period to pass. This can make a later change easier to adjust, but it cannot force every resolver to refresh immediately.
After changing DNS, some users may reach the old host while others reach the new one. Propagation is not a single event or guaranteed countdown. Test from more than one network, device, or DNS lookup service, and allow for caching before declaring the migration complete.
Email preservation
- Confirm that MX records still point to the email provider.
- Preserve SPF and DKIM records unless the email provider specifically instructs you to replace them.
- Keep the DMARC record and review its reporting address if the mail setup has changed.
- Send a test message to the domain and reply from the domain.
- Check both delivery and authentication. A message arriving does not necessarily mean SPF, DKIM, and DMARC are configured correctly.
Use the Business Email DNS Setup checklist when email continuity is important. Never assume that changing nameservers preserves mail records automatically.
Website, SSL, and application checks
Once the new destination is resolving, test the bare domain and the www version, HTTP-to-HTTPS redirects, key pages, images, forms, logins, checkout flows, and important subdomains. Confirm that the new host has issued or installed an SSL certificate for every required hostname. If HTTPS shows warnings or mixed-content errors, consult the SSL Certificate Setup and Renewal guide.
Verification workflow
- Check the authoritative nameservers for the domain.
- Query A, AAAA, CNAME, MX, and TXT records from more than one DNS resolver.
- Load the website over HTTPS from a normal browser and a separate network.
- Confirm that the response is from the new host, using its control panel, server logs, headers, or a temporary marker where appropriate.
- Test email sending and receiving.
- Review monitoring, application logs, analytics, search visibility, and error logs for unexpected changes.
Common mistakes
- Changing nameservers without copying records: This can remove mail, verification, and subdomain records from the active zone.
- Editing DNS at the wrong provider: Changes have no effect if that provider is not authoritative for the domain.
- Leaving an old AAAA record: IPv6-capable visitors may be sent somewhere different from IPv4 visitors.
- Assuming propagation is complete everywhere: Cached answers can persist, particularly when TTLs were not reduced ahead of time.
- Deleting email records during a website move: Website hosting and business email can use separate providers.
- Testing only the homepage: Forms, redirects, APIs, admin areas, and subdomains may fail even when the homepage loads.
- Closing the old host too soon: Keep it available until DNS, email, backups, and application behavior are confirmed.
For a failed cutover, rollback means restoring the previous A, AAAA, or CNAME values, or changing back to the previous nameservers if the old DNS zone remains intact. Make the smallest necessary change, record the time, clear local DNS and browser caches where useful, and retest from multiple networks. Do not repeatedly switch values without identifying which record or service is failing.
When to revisit
Use this checklist before every host migration, new website launch, major DNS change, subdomain setup, or email-provider change. Revisit it before seasonal planning cycles if the site supports time-sensitive campaigns or business operations. It is also worth reviewing after a hosting-panel redesign, a change in DNS provider, the introduction of IPv6, a new SSL workflow, or an update to the organisation's email authentication policy.
Keep the final DNS inventory, backup location, provider contacts, and rollback values in a controlled project record. On the next change, begin by comparing that record with the live zone rather than relying on memory. If you are also moving the domain between registrars, follow the domain transfer checklist separately; registration transfer and DNS cutover are related but distinct tasks.
Action now: identify the authoritative DNS provider, export or document the current zone, verify the new hosting destination, and choose the smallest DNS change that meets your goal. Then schedule the cutover, preserve email records, test from multiple networks, and keep a rollback option until the new site is stable.