Domain registrar
Manages registration, renewal, contacts, locks and transfer controls.
name ownership layer
Website setup
Domain vs web hosting
A domain is the readable name people use. Web hosting is the infrastructure that stores or generates the website. DNS connects the name to that infrastructure.
Try
Live availability across hundreds of extensions. Free, no signup.
The core concept
Name, directions and destination
A working website depends on three separate layers that are often sold in one checkout.
DomainReadable name
›
DNSDirections
›
HostingWebsite destination
You can keep the same domain while changing hosting, or keep the same host while changing the domain. DNS is the connection between them.
The essentials
DNS provider
Publishes the records that route web, mail and other services.
nameservers and records
Web host
Serves static files or application responses when visitors connect.
server · platform · CDN
Website software
Creates the pages and features users interact with.
CMS · app · static site
What you need to publish a website
Buying one layer does not automatically configure the others unless a provider bundles the setup.
Register the domain
Secure the name through an accredited registrar or reseller.
Choose hosting
Select a platform suited to the site's software, traffic and maintenance needs.
Connect DNS
Add the exact records the host provides or delegate DNS carefully.
Enable and test HTTPS
Confirm the certificate, preferred hostname and redirects work before launch.
What changes when you move providers
Identify the layer you are moving before changing nameservers or transfer settings.
| Action | What changes | What can stay |
|---|---|---|
| Move web hosting | Website destination and deployment | Domain registration and email |
| Transfer registrar | Registration management account | Website, DNS and email if delegation stays |
| Change DNS provider | Authoritative nameservers and record management | Registrar and hosting |
| Change domain | Public address, links and email identity | Hosting platform can stay |
Before moving a domain or website
- Export every current DNS record before replacing nameservers.
- Separate website records from MX, SPF, DKIM and other email records.
- Build and test the new host before directing public traffic to it.
- Keep the old host active until DNS caches have moved to the new answer.
- Confirm HTTPS for both the root and www hostnames.
- Use permanent redirects when changing the public domain or page URLs.
Common questions
Do I need both a domain and hosting?
For a conventional public website, yes: you need a reachable name and somewhere to serve the site. Some hosted platforms provide a temporary subdomain, so a custom domain can be added later.
Can I buy the domain and hosting from different companies?
Yes. Point the domain's DNS to the records supplied by the host. Keeping them separate can make future moves clearer.
Will transferring my domain move the website?
No. A registrar transfer changes registration management. If nameservers remain unchanged, the website and email can continue using the same providers.
Will changing nameservers break email?
It can. Replacing nameservers changes the entire authoritative DNS zone, so all required mail and verification records must exist at the new DNS provider.
Keep learning
The next concepts to understand
Next step
Secure the address before choosing a host
Search the domain independently, then connect it to whichever hosting platform fits your site.