Domain and hosting: transfer the name or just point DNS
Checkout will offer to transfer your domain for a dollar and call it simpler. A lot of the time you already have a registrar. Before you move the name, decide whether the host even needs to own it.
I have clicked the cheap transfer at signup because the cart looked tidier with one invoice. Sixty days later I wanted out. The domain was locked. Support wanted the hosting balance cleared first. Nameservers were theirs. The site could have moved in an evening if I had only pointed DNS and left the name where it was. If you are already comparing hosts without leaning on top 10 roundups, pair this with email and DNS ownership and how to choose web hosting without relying on top 10 lists. For why sales copy and review copy so often rhyme, read The Truth About Hosting Review Sites.
The host does not need to be the registrar
A domain name and a hosting account are two products. The name lives at a registrar. Hosting is the box (or the neighbourhood) that answers when someone types the name. You glue them together with DNS: nameservers, or A and AAAA records, plus MX if mail is involved.
Plenty of carts pretend those are one SKU. "Transfer your domain and we'll handle everything." That can mean they become the registrar, they set nameservers to their own, they issue SSL against that zone, and they park mail in the same panel. Fine if you like one login. Ugly if the only unlock button sits behind the hosting invoice you are trying to stop.
Pointing DNS means the name stays at Namecheap, Cloudflare Registrar, Porkbun, wherever you already pay for it. You change nameservers to the host's, or you keep your own nameservers and set A records at the registrar. The site loads from the new box. The registrar bill does not move.
If you are still picking a name from scratch, registering your first domain is the old walkthrough. This post is the checkout fork for people who already own one.
When pointing DNS is the boring win
Keep the registrar and only change DNS when:
- You already like the registrar, the WHOIS contact is actually you, and renewal is a price you can see
- You use Google Workspace, Microsoft 365, or another mail host, and you do not want a signup wizard rewriting MX
- You might leave this web host in a year and you do not want a 60-day transfer lock on the name as well
- You already have Cloudflare (or similar) on the domain and you want to keep that zone
Nameservers vs A records, in plain language:
- Nameservers. The registrar says "ask this host for every record." The host's panel becomes DNS. Easy. You also handed them the zone. Changing MX later means logging into hosting, not the registrar.
- A / AAAA only. The registrar still holds the zone. You point the website hostname at the host's IP and leave MX, SPF, and the rest alone. Slightly more typing. Much easier to undo.
If the host's onboarding will not proceed until you use their nameservers, ask whether A records are supported. "Our platform requires our DNS" is a product choice, not a law of the internet. It is also a hint about AutoSSL and edge caching: they want the zone because the extras live there.
When a transfer is actually fine
Transfer the name to the host when you have a reason, not because the cart discounted it.
Reasons that can be real:
- The current registrar is a mess, support is gone, and you already wanted out
- You understand they will be registrar of record, you can see the renewal price for the domain as its own line, and you can unlock and transfer away without clearing a hosting balance
- You have no mail on the domain yet, and you are fine rebuilding DNS in their panel
A $0.99 first year is not a reason. Renewal pricing for hosting is already a trap. Domain renewal at the host is the same trick on a different SKU. Check year two for the name, not only the plan.
ICANN still puts a 60-day lock on many registrations and inbound transfers. If you transfer at signup and then hate the host in week three, the name may not be allowed to leave even if the site files can. Pointing DNS does not have that lock. Changing an A record back is boring, which is the point.
Ask before you click transfer
Before you buy, send the same short question to every host on your shortlist:
I already have this domain at another registrar. Can I point it with A records or nameservers and leave the domain where it is? If I do transfer it, who is the registrar of record, what is domain renewal in year two, and can I unlock and transfer the name out without paying off hosting first? Is there a 60-day lock after the inbound transfer?
Save the reply. "We'll take care of the domain" is not an answer. "It's easier if you transfer" is a sales preference.
Push on the boring edges:
- Will onboarding overwrite MX if you only wanted the website moved?
- Do they need their nameservers for SSL to renew, or will they issue against A records you control?
- If you cancel hosting, does DNS at their registrar stay editable, or does the zone die with the plan?
- Is WHOIS / registrant contact you, or a privacy proxy you cannot reach when something expires?
This is also a support test. Ask it in chat before you pay. If they will not talk about A records, or they treat "keep the registrar" as a weird request, you have the answer.
If a free migration is on the table, ask whether that offer assumes they also become the registrar. File copies and domain transfers are different jobs. The 2014 version of the move itself is still how to transfer to a new web host. The question now is whether the name has to come along for the ride.
Red flags worth pausing on
Be careful when:
- The cart discounts the plan only if you transfer the domain in the same order
- Chat cannot say who the registrar of record is, or year-two domain pricing
- They will not attach the site unless you change nameservers to theirs
- Unlocking the domain requires a zero hosting balance, a phone call, or a "termination fee"
- The welcome mail talks about "your new domain with us" when you already owned the name last year
Useful hosts will load a site from an A record and leave your registrar alone. Useful reviews mention the Tuesday someone could not transfer the name out. If neither does, you are reading a bundle, not a hosting plan.
We care about this for the same reason we care about email and DNS and migrations: the real product is a hostname you can point at a different box without arguing about who owns the string. Our FAQ on transfer versus pointing DNS is the short version. A domain stuck in a hosting panel is just another sticker.
The best course of action is still the boring one. Keep the registrar unless you have a reason to move it. Ask the same DNS questions of every shortlisted host, try pointing a hostname they did not pre-install if they offer a trial, and treat any discounted transfer as marketing until they show you the registrar and the unlock path. Browse more web hosting guides and keep the homepage ranking list handy while you compare.

