One Roof or Two
Domain and hosting together — one roof or two, argued honestly from the registrar's side
We sell both halves, which is exactly why you should hear the case for splitting them stated fairly — and the case for one roof stated without the usual salesmanship.
The short answer
Together is the right default for most owners: one login, one invoice, delegation set correctly at registration, and support that can see both halves when something breaks between them. The setup fails only when the provider makes leaving hard — so the real test is not 'together or separate' but 'does this company release names on request and let you point nameservers anywhere'.
Separate custody earns its keep at a different scale: an agency holding client sites, a business whose name is too valuable to share a login with anything, or anyone who has been burned before. It costs a little coordination — two renewals, two logins, delegation managed by hand — and buys the certainty that no single account compromise or billing dispute touches both halves at once.
By the Hosting & Domains team · Reviewed 25 August 2026
1 setting
All that couples name to host
Minutes
To repoint delegation anywhere
2 dates
Renewals to track either way
Open
Exits, if the provider is honest
This is the comparison a domains-first company is most often accused of rigging, so let us put the mechanics on the table first. A domain and a hosting account are only connected by delegation: the nameservers set at the registrar decide which zone answers, and the zone's records decide which server serves. That coupling is a setting, not a marriage — changeable in minutes at any competent registrar, wherever each half lives.
Everything else in the debate is about accounts, incentives and failure modes. One roof concentrates convenience and risk in the same place; two roofs distribute both. Neither is wrong. What is wrong is choosing by default without knowing which risks you are accepting — so here are both cases, argued the way we would to a friend.
The case for one roof, without the salesmanship
Convenience is real: registration and delegation happen in one motion, the certificate issues as soon as the name resolves, and renewal dates live on one invoice against one card. Most lapsed domains die of scattered administration, and consolidation is a genuine defence.
Support is the underrated half. When a site is down, the fault line usually runs between DNS and hosting — and a provider that can see both sides of that line fixes in minutes what two providers fix by blaming each other.
The bundle also removes the classic beginner failure: a name delegated to nameservers nobody remembers, with a zone nobody can log into.
The case for splitting, stated fairly
Separation of custody is a security posture. One compromised login at a combined provider exposes the name and the site together; split, an attacker with your hosting password still cannot touch delegation.
It also cleans up disputes. Billing rows, suspensions and provider failures happen; when the name lives elsewhere, the worst any host can do to you is lose the replaceable half. The registrar-held name repoints to a new host in an afternoon.
And it keeps incentives honest. A host that also holds your name has leverage in every disagreement; a host that only hosts competes for the renewal on merit each year.
The failure modes on each side
One-roof failures are concentration failures: an account takeover that gets everything, a payment lapse that suspends both halves, or — the historic sin of this industry — a provider that obstructs departure with release fees and slow codes.
Two-roof failures are coordination failures: the renewal at the forgotten second company, the zone hosted at the old provider after a move, the nameserver change nobody made because each side assumed the other did.
Notice both lists are administrative, not technical. The machinery works fine either way; what fails is bookkeeping and, occasionally, provider ethics.
The setup that works under either answer
Register the name in your own details whichever roof it lives under — the registrant record, not the account, is what makes it yours.
Keep the zone somewhere you can log into, know its nameservers by name, and export a copy of the records whenever they change. Delegation knowledge is the entire coupling; write it down.
Then test the exit before you need it: confirm the registrar releases auth codes on request and the host allows full backups out. Providers that pass both tests make the together-or-separate question pleasantly low-stakes — which is the position to buy from.
Our interest, declared and constrained
We would rather hold both halves of your setup, and we make money when you let us — declared plainly. The constraint we accept in return: names registered here are recorded in your details, released on request the moment registry locks allow, and free to delegate to any nameservers on earth, including a competitor's, while remaining registered with us.
That constraint is what makes the recommendation honest. Together-at-a-provider-you-can-leave gives you nearly all the safety of splitting with none of the coordination cost. Together-at-a-provider-that-traps-you is the worst of every option — and no bundle discount prices that risk correctly.
- Registrant record in your details, whichever roof you choose
- Nameservers pointable anywhere, no penalty, no ceremony
- Auth codes and IPS tags released on request
- Full site backups exportable whenever you ask
Why Hosting & Domains
Standard on every plan
One roof, exits open
Both halves in one account for daily convenience, with the name yours to move the day we stop deserving it.
Delegation set correctly at birth
Register and host together and the nameservers, zone and certificate are aligned before you touch a setting.
Split custody supported, not punished
Host here with the name elsewhere, or the reverse — either way support treats the whole delegation chain as its problem.
One calendar for both renewals
Hosting and registration dates on one invoice if together — and clearly labelled reminders if you split.
Quick Start
Order placed to site online
- 1
Choose your risk, not a slogan
Concentration risk with convenience, or coordination cost with separation. Either is sound once chosen knowingly.
- 2
Fix the constants
Your details on the registration, the zone's location written down, records exported — true under any arrangement.
- 3
Test the exits
Ask for the auth-code policy and a backup export before committing. Providers that pass make the whole question low-stakes.
Built In
Fitted to every plan
- Registration in your own details, never the provider's
- Nameserver delegation documented in one written line
- Zone records exported after every meaningful change
- Auth-code release policy confirmed before purchase
- Renewal dates for both halves on one calendar
- Account security strongest wherever the name lives
Frequently Asked
The questions that come up most
Is it actually risky to keep the domain and hosting at one company?
The risk is real but specific: one login and one billing relationship control both halves, so an account compromise or a payment dispute has a wider blast radius. At a provider that releases names freely and lets you repoint delegation at will, the residual risk is modest and most owners rightly accept it for the convenience. At a provider that obstructs exits, the same setup is a trap.
If I buy them together, can I later move just one half?
Yes — that is the whole point of delegation. Move the hosting by pointing the zone's records at the new server, or the nameservers at the new provider, while the registration stays put. Move the registration by auth-code transfer while the site keeps serving untouched. The two halves were never technically fused; only the billing was shared.
Does hosting elsewhere from the registrar slow my website down?
Not measurably. Resolution follows the delegation chain wherever it points, and a visitor's resolver caches the answer either way — the zone's location matters far more for management convenience than for speed. Choose DNS hosting for reliability and editability; choose web hosting for performance; they need not be the same company.
Whose nameservers should the domain use — the registrar's or the host's?
Whichever zone you will actually maintain, because the nameservers decide where record edits must happen. Hosting with us and the simplest answer is ours: the zone lives in cPanel next to the site. Split setups usually run the host's nameservers for web convenience, or a third-party DNS layer for independence. Any of these is fine — what breaks things is not knowing which one you chose.
What is the single most important protection under either arrangement?
The registrant record. A name registered in your details survives provider failures, account disputes and bad decisions on either side, because the registry answers to the registrant. Names registered in a provider's or designer's details are the ones that turn into hostage negotiations — that, far more than together-versus-separate, is the mistake that costs people their name.
Keep reading
Web Hosting
The hosting half: cPanel on NVMe, with delegation aligned at registration if you take both.
Domain Names
The permanent half: registered in your details, pointable anywhere, released on request.
Transfer a Domain
Consolidating after the fact — bring the name to the roof the rest of the setup lives under.
Email at Your Domain vs Free Email
The third tenant under the same roof decision: where the mailboxes should live.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
One roof if we earn it. Exits open regardless.
Register and host together with the name in your details and every door unlocked — or split custody and we will serve our half properly.
View Domain Names plans