Domain Registrar vs. Web Hosting: What Each Does and Why You Keep Them Separate
One of the most common mistakes when starting a website is treating "domain registration" and "website hosting" as the same thing. They are jobs done by two different companies, like buying a house: the domain is the "property title" you own (handled by the registrar), and hosting is the house itself (handled by the host). You can buy from company A and let company B manage the property — the domain stays at the registrar while the website files live at the host. This guide explains both roles, why you keep them separate, and the key points of transfers and renewals.
What each one manages
- Domain registrar: Manages the "title record" of your domain — which domain you own, when it expires, WHOIS contacts, and which DNS servers it points to. It provides registration, renewal, transfer, and DNS settings.
- Web hosting: Provides the "home" for your website — stores the site files and database, and allocates CPU, memory, and bandwidth so visitors can load your pages. This can be shared hosting, a VPS, a cloud server, or a dedicated server; for help choosing, see website hosting type selection.
The two are linked by one "bridge": the DNS records under your domain. At the registrar, your domain resolves to the host's IP address, so when a visitor types your domain, they find the website on the host. To understand how DNS works, see domain DNS records basics.
Should the domain live at the registrar or the host
Recommendation: always keep the domain at the registrar; the host only "rents" space for your site. Three reasons:
- Change hosts without changing the domain: When the site moves (changes hosts), just update the DNS pointer — the domain does not move and visitors notice nothing. For moving the site itself, see the website migration guide.
- Avoid being "held hostage": Some hosts register domains with locks or auto-renewal clauses, so when you want to leave, the domain will not come with you.
- Registrars are more specialized: Renewal reminders, WHOIS privacy, and the authorization code (EPP Code) for transfers all live on the registrar side.
Comparison table
| Dimension | Domain registrar | Web hosting |
|---|---|---|
| Manages | Domain registration, renewal, transfer, WHOIS, DNS | Site files, database, bandwidth, runtime |
| Analogy | Land title office | Property manager / house |
| Your core asset | The domain itself | Site data and operation |
| Switching away | Domain transfer, more paperwork | Just change the DNS pointer, nearly seamless |
| Typical trap | Letting it lapse and getting squatted, being locked | Data held hostage, no backup on expiry |
Domain transfer and renewal points to remember
- Before transferring: Unlock the domain, disable the transfer lock, and get the EPP code from your current registrar; domains registered less than 60 days ago, or right after a renewal, usually cannot be transferred.
- During transfer: The new registrar typically adds a year of renewal, and you should avoid major DNS changes during the transfer to prevent resolution downtime.
- Renewal: Enable auto-renew and handle it 1-3 months ahead; after expiry there is usually a 30-day grace period, then a costly redemption period. For renewal strategy, see domain renewal strategy.
- Security: Turn on two-factor authentication and WHOIS privacy at the registrar, and make sure the contact email works — many domain "thefts" start with a compromised email. For the full flow, see the domain transfer guide.
- Picking a registrar: Compare price, renewal price, transfer freedom, and support response — do not chase only the first-year discount. See the domain registrar selection guide.
A typical scenario: a website from scratch
Say you are building a photography portfolio site. The full division of labor looks like this:
- Registrar: Register
lensfolio.com, enable auto-renewal and WHOIS privacy, and make sure the contact email is yours and can receive mail. - Host: Buy a cloud server or shared hosting, put the site files and database on it, and configure the domain to resolve to the host IP.
- DNS layer: At the registrar or a managed DNS, point an A/CNAME record at the host; you can add a CDN for speed without touching the domain.
- When moving: Only change the DNS pointer, migrate files and the database from the old host to the new one (see the website migration guide), and the domain is untouched throughout.
- When renewing: The domain auto-renews at the registrar and the site data is backed up at the host — the two never interfere.
This example makes it clear: the domain is "title," the host is "use." Keeping them separate leaves you free to move either way.
FAQ
Q1: Can I buy domain and hosting from the same company? Yes, it is convenient and beginner-friendly, but strongly keep the domain in a registrar account so you can move it anytime.
Q2: Can I manage DNS at the host's panel? Yes, many hosts offer domain management panels, but the "title" still belongs to the registrar — resolving is just a hosting service.
Q3: Will I lose the domain when changing hosts? No. As long as the domain is in the registrar's name, change the DNS pointer and the site stays up.
Q4: Can I recover a domain deleted after I forgot to renew? Within the redemption period, yes, but it is expensive; after that you wait for open registration, which costs even more. So always enable auto-renew.
Q5: Can the domain and host use vendors in different countries? Absolutely. Domains are global and hosts are chosen by business region; just mind compliance like ICP filing for mainland China hosting and domain real-name verification.