
A domain name and hosting are two separate services linked by DNS. The difference between them, two ways to point a domain to hosting, the steps, email, delays and whether to use one or two providers.
By Mouhamed BANKOLE, CEO at ITNET Technologies · Updated October 29, 2026 · Reading time: 10 min
You registered a domain name in one place, signed up for hosting somewhere else, and your address still shows a "parked domain" page. Or you are wondering whether to buy everything from the same provider. To connect a domain to hosting, you link two separate services through DNS so that your website appears. This guide explains the difference between the two, the two ways to point a domain to hosting, the concrete steps, and how to choose between one or two providers.
In short
- The domain name is the address (yoursite.com), the hosting is the server where the site's files and database live.
- DNS makes the link: it tells browsers which IP address answers for your domain.
- Two ways to connect them: change the domain's nameservers at the registrar, or keep the DNS zone and edit the A, AAAA and CNAME records.
- One provider keeps things simple; two providers give you more independence, as long as you document who manages the DNS zone.
- The change is not instant: resolvers keep the old value in cache until its time to live (TTL) expires.
Contents
- What is the difference between hosting and a domain name?
- How does a domain name find its hosting?
- What are the two ways to connect a domain to hosting?
- How do you point your domain to your hosting, step by step?
- Should you buy hosting and the domain from the same provider?
- What happens to email when you connect the domain to new hosting?
- How long does it take for the domain to point to the site?
- How do you check that the domain points to the hosting?
- How do you change hosting without changing your domain name?
What is the difference between hosting and a domain name?
The domain name is the address your visitors type, the hosting is the server space that stores and serves your website: you need both, and they are two separate contracts. A simple picture: the domain is the street address, the hosting is the building.
- The domain name is rented yearly from a registrar, which registers it with the registry of the extension (.com, .fr…).
- The hosting is rented monthly or yearly from a hosting provider: disk space, database, PHP, SSL certificate, backups.
- DNS (Domain Name System) is the directory that links the two: without it, the domain does not know which server to send visitors to.
| Item | Domain name | Web hosting |
|---|---|---|
| Role | Address of the site and email | Stores and serves the site |
| Provider | Registrar | Hosting provider |
| Term | Yearly rental, renewable | Monthly or yearly plan |
| What you set there | Nameservers, DNS zone, transfer lock | Files, databases, PHP version, SSL |
| Works on its own? | No: without hosting, blank or parked page | Yes, but only through an IP address or a technical URL |
To go further on each building block, read our web hosting guide and our guide to choosing and keeping a domain name.
How does a domain name find its hosting?
The browser asks DNS for the IP address tied to the domain, then connects to the hosting server at that address. Everything happens in the domain's DNS zone.
A visit, simplified:
- The visitor types yoursite.com in the browser.
- A DNS resolver looks up which nameservers are authoritative for that domain (the ones set at the registrar).
- Those servers answer with the site's A record (IPv4 address) or AAAA record (IPv6 address), record types defined in IETF RFC 1035 and its successors.
- The browser connects to that IP address, and the hosting server returns the page for the requested domain.
Pro tip: your hosting must also "know" the domain. Add it as the primary domain or an addon domain in the hosting control panel, otherwise the server will return a default page even when DNS is correct.
What are the two ways to connect a domain to hosting?
You can either hand the whole DNS zone to the host by changing the domain's nameservers, or keep the zone at your registrar and edit only the records that point to the site. Both work; they do not give you the same level of control.
| Method | What you change | Benefits | Watch out for |
|---|---|---|---|
| Change the nameservers (NS) | The nameservers set at the registrar | The host configures everything: site, email, SSL | The whole zone moves: recreate your MX, SPF, DKIM and TXT verification records |
| Edit the A/AAAA/CNAME records | A few lines of the existing DNS zone | You keep control of the zone and email | You need the hosting IP and must update it if it changes |
- Changing nameservers suits you when the host also handles your email or you want everything in one place.
- Editing records suits you when email lives elsewhere (Microsoft 365, Google Workspace, another provider) or several services share the same domain.
How do you point your domain to your hosting, step by step?
Get the nameservers or the IP address from your host, enter them where your domain is managed, then add the domain to your hosting account. Expect about ten minutes of work, not counting the time DNS takes to update.
Method 1, with nameservers:
- Write down the nameservers given by the host (often two or three names like ns1.host.tld).
- Export your current zone at the registrar (screenshot or file), so you lose no MX or TXT record.
- Replace the nameservers in your registrar account, under "Nameservers" or "DNS servers".
- Recreate in the new zone the email and verification records you had.
Method 2, with records:
- Find the IP address (IPv4, and IPv6 if provided) of your hosting in its control panel.
- Edit the A record of the bare domain (@) with the IPv4, and the AAAA record with the IPv6.
- Point www to the bare domain with a CNAME, or to the same IP with an A record.
- Lower the TTL a few hours before the change if you are moving an existing site, to speed up the switch.
Final step for both: add the domain in the hosting control panel and request the SSL certificate, which can only be validated once DNS is in place.
Note: a CNAME is not allowed on the bare domain, because it cannot coexist with the other apex records, as RFC 1912 points out. Use an A or AAAA record for @.
Should you buy hosting and the domain from the same provider?
One provider is the simplest choice for a brochure site or a blog; two providers make sense if you want to be able to change hosts without touching the domain. It is not a technical requirement: any domain can point to any hosting.
With one provider:
- one invoice and one support team for the domain, the site and often email;
- the connection is automatic: no nameservers to copy;
- a domain may be included: for example, yearly Wayhost web hosting plans include a free domain for the first year and free migration (checked on October 29, 2026).
With two providers:
- you keep ownership of the address even if there is a dispute or you leave the host;
- changing hosts means editing a few records, with no domain transfer;
- you must know who manages the DNS zone, and renew two contracts on different dates.
Either way, check that the domain is registered in your name (registrant), not in the name of an agency or contractor.
What happens to email when you connect the domain to new hosting?
Email depends on the MX records in the DNS zone, not on the site's hosting: it keeps working if you only touch the A records, but it can stop if you change nameservers without copying the MX records. This is the most common failure when the change is poorly prepared.
- MX: names the server that receives mail for the domain.
- SPF (TXT record): lists the servers allowed to send for your domain.
- DKIM (TXT or CNAME): publishes the key that signs your messages; see our DKIM and SPF guide.
- TXT verifications: Google, Microsoft and other services store their validation codes there.
If you want mailboxes on your domain that do not depend on the site's hosting, a professional email plan is set up with its own MX records in the same zone.
How long does it take for the domain to point to the site?
A record change becomes visible once resolvers have dropped the old value, that is, when its TTL expires; a nameserver change usually takes longer, because it also goes through the extension's registry. This is what people call "DNS propagation".
- Changing an A or CNAME record: the delay equals the TTL of the old record, a cache duration that RFC 1035 defines in seconds.
- Changing nameservers: you also wait for the NS records cached at the extension level to expire.
- During the switch, some visitors see the old site and others the new one: keep the old hosting active until the transition is complete.
How do you check that the domain points to the hosting?
Query DNS with dig or nslookup and compare the IP address you get with the one shown by your host. If they match, DNS is fine; if the site still does not load, the problem is on the hosting side.
| Check | Command or tool | Expected result |
|---|---|---|
| Site IPv4 address | dig +short yoursite.com A | The hosting IP |
| www subdomain | dig +short www.yoursite.com | The bare domain or the same IP |
| Active nameservers | dig +short NS yoursite.com | The expected nameservers |
dig +short MX yoursite.com | Your mail servers | |
| SSL certificate | Browser padlock | Valid certificate for the domain |
- Flush your local DNS cache (
ipconfig /flushdnson Windows) before drawing conclusions. - Test from a mobile network to bypass your router's cache.
How do you change hosting without changing your domain name?
Copy the site to the new hosting, test it, then edit the A/AAAA records (or the nameservers): the domain stays with its registrar and does not need to be transferred. A domain transfer is a separate operation, only useful if you also want to change registrars.
- Back up the site and its database at the old host.
- Install it on the new hosting and test it through a temporary URL or the hosts file.
- Lower the TTL, then edit DNS.
- Cancel the old hosting only after the switch is complete, email included.
If you also want to bring the domain to your host, a domain transfer uses the authorization code (AUTH code) provided by the current registrar. After a change of registrant, a registrar may block transfers for 60 days, as allowed by the ICANN Transfer Policy. At Wayhost, full DNS management (A, MX, CNAME, TXT), DNSSEC and unlimited subdomains come with domain names (checked on October 29, 2026). For a growing site, our guide to moving from shared hosting to a VPS follows the same logic.
Frequently asked questions
What is the difference between a domain name and hosting?
The domain name is your site's address, the hosting is the server that stores its files. They are two separate services, linked by DNS. You need both for a website to appear.
Can you have a domain name without hosting?
Yes, a domain name can exist on its own. It can then be used for a redirect, for email or to protect a brand. Without hosting, no website appears at that address.
Can you connect a domain bought elsewhere to your hosting?
Yes, any domain can point to any hosting. You just change the domain's nameservers or edit its A record at the registrar. Then add the domain in the host's control panel.
Do you need to transfer your domain to change hosts?
No, changing hosts does not require a domain transfer. You only edit DNS so that it points to the new server. A transfer is only for changing registrars.
Why does my domain still show the old site?
DNS resolvers keep the old address in cache until the TTL expires. Flush your computer's cache and test from another network. If the problem persists, check the A record with dig or nslookup.
Will my email stop if I change nameservers?
It can stop if the MX, SPF and DKIM records are not recreated in the new zone. Export your zone before the change and copy those lines. If you only edit the A record, email is not affected.
What is an A record?
It is the line in the DNS zone that maps a domain name to an IPv4 address. Its IPv6 equivalent is called AAAA. It is the record you edit to point a domain to hosting.
Is it easier to buy everything from the same provider?
Yes, the connection is then automatic and you deal with a single support team. On the other hand, leaving the host takes a little more preparation. In every case, check that the domain is registered in your name.
Key takeaways
- The domain is the address, the hosting is the server: two separate services linked by DNS.
- Two methods: change the domain's nameservers, or edit the A, AAAA and CNAME records.
- Email depends on MX records: export the zone before any nameserver change.
- The switch follows the TTL: lower it before a migration and keep the old hosting active during the transition.
- Changing hosts does not require a domain transfer, but always check that the domain is registered in your name.
To manage your site and its domain from a single dashboard, discover Wayhost web hosting.
Article written by Mouhamed BANKOLE, CEO at ITNET Technologies.