Registrar vs DNS vs Hosting: What's the Difference?
Three different jobs. The registrar holds your legal claim to the name and bills you for it. DNS is the directory that translates the name into server addresses. Hosting is the server your website actually runs on. They can be — and often should be — three different companies, and you can change any one without touching the other two.
This is the single most useful piece of infrastructure literacy a business owner can hold, because almost every domain-related panic ("the site is down!", "email stopped!", "the agency left and took the website!") is a confusion about which of the three layers broke and which company to call. Learn the map once and you stop being hostage to whoever set it up.
What does a registrar actually do?
A registrar is where a domain is registered — the company accredited to record, in the global registry for your TLD, that this name belongs to you for a paid term. Your registrar account controls the three things that matter most: the registrant contact (who owns it, as a practical matter), the nameserver setting (which DNS provider answers for the domain), and the transfer controls (locks and auth codes).
What the registrar does not do: serve your website, route your email, or store your DNS records — unless you also happen to use its bundled DNS. The registrar's job is ownership and pointing, nothing more. That's also why registrar choice is mostly a question of price and security, not performance — and why paying a retail markup buys you literally nothing, as covered in what it costs to stay at GoDaddy.
What does DNS actually do?
DNS is the phone book. When someone types your domain or emails your address, their software asks your domain's nameservers: "where do I go?" The nameservers answer from your zone's records:
| Record | Question it answers |
|---|---|
| A / AAAA | What server IP does this name point to? |
| CNAME | This name is an alias for which other name? |
| MX | Which mail servers accept email for this domain? |
| TXT | Verifications and email authentication (SPF, DKIM, etc.) |
Whoever runs your nameservers controls where your domain points — which is why moving DNS deliberately, record by record, is the heart of a zero-downtime migration, and why a fat-fingered DNS change can take down a site whose hosting is perfectly healthy.
What does hosting actually do?
Hosting is the building at the address DNS hands out — the server or platform running your website's actual code and files. Vercel, a WordPress host, Shopify, a VPS: all hosting. Your email service (Google Workspace, Microsoft 365) is effectively a fourth layer: mail hosting, reached via MX records, fully independent of your web host.
Why does the separation matter in practice?
- You can change hosts without touching the domain. New website platform? Update one DNS record. No transfer, no registrar involvement.
- You can change registrars without downtime. The registration moves; DNS keeps answering. This is the entire basis of the no-downtime transfer method.
- You know who to call. Site down but domain resolves → hosting. Nothing resolves → DNS. Renewal or transfer question → registrar. Email bouncing → MX records or mail provider.
- You can audit control. "Who has the registrar login?" is a different — and more important — question than "who built the website." Many owners discover the answer is their agency, which is its own problem: should your agency own your domain?
What's the right architecture for a business owner?
There's no single answer, but there's a sane default: registrar and DNS together at an at-cost, security-first provider; hosting wherever your product needs to live. Cloudflare happens to collapse the first two layers cleanly — its registrar requires its DNS, charges wholesale for the registration, and includes DNSSEC and WHOIS privacy at no charge. Your hosting stays wherever it is; only the pointing and the ownership move.
What you're avoiding is the opposite pattern: everything bundled at a retail registrar because that's where the domain happened to be bought. Bundles concentrate risk in one account, hide which layer does what, and bill a premium for the opacity.
FAQ
Can my registrar and my DNS provider be different companies?
Yes, and it's completely normal. The registrar stores which nameservers your domain uses; those nameservers can belong to anyone. Point them at a different DNS provider and that provider now answers all queries for your domain, while the registration stays where it is.
If I change my website hosting, do I need to transfer my domain?
No. Changing hosts means updating the DNS records that point at the old server — usually an A record or CNAME — to point at the new one. The domain registration doesn't move at all. This confusion causes a lot of unnecessary domain transfers.
Which company controls whether my email works?
Your DNS provider, via the MX records, plus whoever runs your mail service (like Google Workspace or Microsoft 365). Email is not tied to your web host or your registrar. If MX records are correct, email flows no matter where the domain is registered or the site is hosted.
Is it bad to buy domain, DNS, and hosting from one company?
It's convenient but it concentrates risk and usually cost: one account outage or dispute affects everything, and bundled convenience is typically priced at a premium. A common architecture for business owners is registrar and DNS together at an at-cost provider, with hosting wherever your stack actually needs to run.