HostingReview Lab
Open navigation

Domain Transfer vs. DNS Change: Which One Do You Need?

Edited by Avery Stack · Technical Hosting EditorUpdated September 25, 2026 · Illustrated editorial persona · About our editorial voices

If you are moving a website to a new host, you usually do not need to transfer the domain registration. You can point the existing domain at the new website using DNS. A registrar transfer, a nameserver change, and a DNS record edit are three different jobs. Knowing which one you need can save a lot of unnecessary work.

Three changes that people call “moving a domain”

  • Change a DNS record: Edit the website’s A, AAAA, or CNAME record at the DNS provider that currently manages the domain. The registrar and nameservers can stay where they are. This is often enough when only the website host changes.
  • Change nameservers: Move responsibility for the domain’s DNS zone to a different DNS provider. This does not itself transfer the domain registration. Re-create and verify the website, email, verification, and other records at the new DNS provider before switching nameservers.
  • Transfer the domain registration: Move the domain to a new registrar for management and renewal. The website files, hosting subscription, and mailboxes do not move with the registration.

These can be separate decisions. ICANN explicitly distinguishes changing a host’s IP address or nameservers from transferring a registration. HostGator’s support guide makes the same distinction for hosting customers.

If you only want to move the website

Keep the domain at its current registrar and keep its current DNS provider unless you have a reason to change either. Build the site at the new host, test it, then update only the records that direct web traffic to the old host. Your new host should tell you the exact target and which records to change for the root domain and www.

Before changing a record, save the current DNS zone and note which service handles email. An A or CNAME edit for the website usually does not require an MX change when mail is hosted elsewhere. First check where the existing MX target resolves: if it points to the same hostname or IP used by the website, changing that web record can also interrupt mail even though the MX record itself stays the same. Also check TXT records used for SPF, DKIM, DMARC, search verification, and other services; leave them in place if those services are staying. Cloudflare’s email DNS guide explains why mail delivery and sender authentication need their own records.

For a complete move, use our website migration checklist. It covers files, databases, testing, rollback, and keeping the old host online while the new site is checked.

When would you change nameservers?

Change nameservers when you want a different company to manage the entire DNS zone. This can make sense if your current DNS provider is closing, you want Cloudflare to manage DNS, or your chosen platform requires its DNS service. It is a bigger change than editing a website record because the new provider must answer for all the domain’s DNS records.

  1. Export or record the current zone, including A, AAAA, CNAME, MX, TXT, SRV, and any other records you use.
  2. Add the needed records at the new DNS provider and compare them with the original, especially mail and verification records.
  3. Check DNSSEC instructions for the two providers before changing delegation; a stale DS record can prevent the new zone from resolving.
  4. Change the assigned nameservers where the registration is managed, then verify the website and email from more than one network.

Cloudflare’s full DNS setup instructions describe the zone review and nameserver change, including the DNSSEC step. Nameserver controls can vary by registrar; Cloudflare Registrar, for example, requires its own nameservers while a domain is registered there.

When would you transfer the registration?

A registrar transfer is for changing the company that manages the domain registration and renewal. Reasons might include account consolidation, support, security controls, or renewal terms. It is not necessary merely to change web hosting. Check whether the domain is eligible to transfer, whether it is locked, and what the destination registrar will charge before starting.

For many generic top-level domains, the process involves unlocking the domain, obtaining a transfer authorization code from the current registrar, starting the request with the new registrar, and approving required notices. ICANN’s registrant transfer FAQ covers the steps and common blocks, including certain 60-day transfer restrictions. Rules for a specific country-code domain or registrar may differ, so check both providers before planning a date.

Write down who will manage DNS after the transfer. A change of registrar does not guarantee that the destination will host an identical DNS zone. Confirm that the nameservers and records still serve the website and email when the transfer completes. If the current registrar also provides your DNS, ask what happens to that DNS service when the registration leaves.

A simple decision guide

  • “I bought hosting somewhere else, but I want to keep my domain company.” Test the new site, then update the website DNS records.
  • “I want Cloudflare or another company to manage all my DNS.” Copy and check the full zone, then change nameservers. The domain registration can remain where it is.
  • “I want a different company to bill and manage my domain registration.” Plan a registrar transfer. Verify DNS continuity and the transfer rules separately.
  • “I want all three.” Treat the website move, DNS move, and registrar transfer as separate changes. Finish and test one before the next so you can tell what caused a problem.

What to verify after any change

Load the website over HTTPS on the root and www versions; check forms and any checkout or login. Send and receive a test email using the domain. Our website move and email checklist covers the MX, SPF, DKIM and nameserver checks in more detail. Confirm the authoritative nameservers, website records, and mail records point where you intended. Keep the old hosting service until the new setup has worked through the site’s normal activity.

If you are still separating the basics, start with domain name versus web hosting. If a move is tied to a refund window, read the renewal-cost guide before you cancel a paid term.

Related guides