Domain vs DNS vs Hosting: What Each One Actually Does

Three separate things, three separate bills, and they can come from three different companies.

• The domain is the name you rent, like example.com.
• Hosting is the computer your website’s files sit on.
• DNS is the directory that tells the internet which computer that name points to.

The usual analogy is that the domain is your address, hosting is the house, and DNS is the phone book. It works, but it stops being useful the moment something breaks.

This guide goes past the analogy to the parts that actually cost people money: who really owns your domain, why moving your website can kill your email overnight, and why “DNS propagation” is not the thing you have been told it is.

Quick Comparison

The last row is the one worth remembering. All three are independent, so a problem with one does not have to mean touching the others.

The Domain: What You Are Actually Buying

You are not buying a domain. Domain registration is a rental: you hold the exclusive right to use a name, normally a year at a time, through a registrar accredited by ICANN.

Stop paying and the name goes back into circulation for someone else to register. There is no permanent ownership on offer at any price.

The registrar is just a shop. Namecheap, GoDaddy, Cloudflare and your hosting company are all selling the same underlying thing at different prices with different interfaces.

Because the name is separate from everything else, you can move your entire website to a new host and keep the same domain. Visitors never notice, and your domain history stays intact.

Watch the Renewal Price, Not the First-Year Price

Introductory pricing on domains is aggressive. A name advertised at a pound or two for year one often renews at ten or twenty times that.

Before registering, find the renewal price rather than the headline. You will pay it every year afterwards, and moving a domain to escape a bad renewal rate is more hassle than choosing correctly at the start.

Once the name is registered, there is a short list of things worth doing straight away. We covered those separately in what to do after buying a domain.

Who Actually Owns Your Domain?

This is the most expensive thing on this page and none of the guides ranking for this question mention it.

When an agency, a web designer or a friend-who-does-computers sets up your site, they frequently register the domain in their own name, on their own registrar account, paid on their own card.

Everything works fine, so nobody notices. Then the relationship ends, or they stop answering, or they go out of business. Now the name your customers know, your email addresses and your search rankings all sit inside an account you cannot access.

Check It in Two Minutes

Look up your domain in any WHOIS lookup. You are checking the registrant, which is the legal holder. The admin and technical contacts matter less.

If privacy protection is on, the registrant will show as a proxy service, which is normal and good. In that case log into the registrar account directly instead. If you cannot log in, you have found your problem.

Fixing It

The clean fix is to have the domain transferred to a registrar account in your own name, with your own billing details.

Two things to expect. You will need an authorisation code, sometimes called an EPP or auth code, from the current registrar. And a 60-day transfer lock commonly applies after a change of registrant, which is an anti-hijacking measure and cannot be shortened once it starts.

Some registrars let you opt out of that lock if you ask before making the change, so plan the sequence rather than discovering it halfway through.

Do this while everyone is still on good terms. It is a routine administrative task then and a serious problem later.

Hosting: What You Are Paying For

Hosting is disk space, memory and processing on a server that stays switched on, connected and backed up.

The tiers are mostly about how much of that machine is yours. Shared hosting splits one server among many sites, VPS gives you a guaranteed slice, and dedicated gives you the whole machine.

Hosting Is a Ranking Factor, Indirectly

Nobody at Google is grading your host. But hosting decides how fast your server responds, and that is measured.

Time to first byte, the delay before your server sends anything at all, is set almost entirely by your hosting. No amount of image compression or caching plugin work fixes a slow server underneath.

Server location matters too. A UK audience served from a US data centre pays a physical latency cost on every request that no speed optimisation can undo.

If your site feels slow before anything has loaded, look at the host before the plugins.

DNS: The Part Everyone Finds Confusing

DNS translates names into numbers. Someone types your domain, DNS returns an IP address, and the browser goes to that address.

Where it gets confusing is that there are two separate layers, and people mix them up constantly.

Nameservers vs Records

Nameservers decide which company answers DNS questions about your domain. They are set at your registrar and look like ns1.somehost.com.

Records are the individual answers, and they live wherever your nameservers point.

The practical consequence: if you change nameservers, you have moved your entire DNS setup to a different provider, and any records you had configured at the old one stop applying. This is why a site sometimes disappears after someone “just pointed the domain at the new host”.

The Four Records You Will Actually Touch

• A record, points a name at an IP address. This is what sends your domain to your web server.
• CNAME, points a name at another name. Used for things like www, or when a service tells you to point a subdomain at theirs.
• MX record, says which server handles email for your domain. Completely separate from your website.
• TXT record, holds text. Used to verify domain ownership with Google or Microsoft, and for email authentication like SPF, DKIM and DMARC.

That is genuinely most of it. Everything else you will meet occasionally, but these four cover normal life.

Moving Your Website Can Kill Your Email

This is the single most common self-inflicted disaster in this whole area, and it follows directly from the point above.

Your website and your email are separate services that happen to share a domain name. The A record sends visitors to your web host. The MX records send email to your mail provider, which is often Google Workspace or Microsoft 365, not your host at all.

When you move hosts, the new host tells you to change your nameservers to theirs. You do. The website comes up and everything looks like a success.

But your DNS is now being answered by the new host, using their default records. Their default MX records point at their own mail service, which has no idea about your mailboxes.

Email stops arriving. Worse, senders often get no bounce, so you do not find out until someone asks why you ignored them.

How to Avoid It

Before changing nameservers, open your current DNS panel and write down every record. Screenshot the whole zone.

Pay particular attention to MX records and any TXT records for SPF, DKIM, DMARC or service verification. Those are the ones that silently break things.

Then, after switching, recreate every one of them at the new provider before you consider the migration done.

Better still: leave DNS where it is. You do not have to move DNS just because you moved hosting. Changing a single A record to the new server’s IP is a smaller, safer change than moving nameservers.

“DNS Propagation” Is Mostly a Myth

You will be told a change takes 24 to 48 hours to propagate around the world. That is not really what happens.

DNS changes take effect at the source immediately. What causes the delay is caching. Every DNS record carries a TTL, a time-to-live value in seconds, which tells other servers how long they may reuse the answer before asking again.

If your A record has a TTL of 86400, that is 24 hours, then a resolver that looked it up an hour ago will keep serving the old answer for another 23. Nothing is travelling anywhere. It is just remembering.

The Trick That Makes Migrations Painless

Lower the TTL before you make the change, not after.

Drop the TTL on the records you are about to change to 300 seconds, five minutes, and wait for the old TTL to expire. If it was 24 hours, wait a day.

Now make your actual change. Because everything is caching for only five minutes, the switch happens within minutes rather than a day or two.

Once you are happy, put the TTL back up to something normal to reduce lookups.

This one habit turns a nervous overnight migration into a lunchtime job, and it is why “wait 48 hours” is advice for people who did not plan.

Where Cloudflare Fits

Cloudflare confuses this topic because it sits in the middle of all three without being any of them.

Most people use it as their DNS provider. You point your nameservers at Cloudflare and manage records there instead of at your host or registrar.

It also acts as a proxy in front of your site, which is where the caching, the CDN and the security filtering come from. When that proxy is on, the IP the world sees is Cloudflare’s, not your server’s.

That last detail catches people out. A record can look correct while the site still serves from cache, and diagnostic tools report Cloudflare’s IP rather than your host’s.

Cloudflare also sells domains as a registrar, so it is entirely possible to have all three functions with them and still have a completely separate hosting company. That is a normal, sensible setup.

Should You Buy Everything From One Company?

Hosting companies bundle a free domain because it makes leaving harder. That is not a reason to refuse, but it is worth knowing why the offer exists.

Together is simpler. One bill, one login, one support number, and the setup is usually done for you.

Separate is safer. If your host has an outage, a billing dispute or you simply want to leave, your domain is not held in the same account as the thing you are arguing about.

The middle path that most experienced people settle on: keep the domain at a dedicated registrar, keep DNS somewhere reliable, and treat hosting as the replaceable part. Hosting is the piece you are most likely to change.

Three Separate Clocks

Domain renewal, hosting renewal and any SSL certificate all expire on their own schedules, and each fails differently.

• Hosting expires: site goes offline, files usually recoverable for a while.
• SSL expires: visitors get a security warning, which frightens them more than a plain outage.
• Domain expires: the worst one. Site and email both stop, and after a grace period the name can be bought by anyone.

Turn on auto-renew for the domain, and make sure the card on file is one that still exists. Expired-card failures on forgotten registrar accounts lose more domains than deliberate decisions do.

Keep the registrar’s contact email at an address that does not depend on the domain itself. If the domain lapses and your only contact address is you@thatdomain.com, the warning emails go nowhere.

Frequently Asked Questions

Do I need to buy hosting and a domain from the same company?

No. They are separate services and can come from different providers. Buying together is simpler to set up, while keeping them separate means a dispute or outage with your host does not affect control of your domain name. Many experienced site owners keep the domain at a dedicated registrar and treat hosting as the replaceable part.

What is the difference between a domain and DNS?

The domain is the name you rent, such as example.com. DNS is the directory system that translates that name into the IP address of the server holding your site. You can keep the same domain while changing your DNS provider, your hosting, or both.

Why did my email stop working after I moved hosting?

Almost certainly because changing nameservers moved your DNS to the new host, which applied its own default records including MX records. Those point at the new host’s mail service rather than your actual mail provider. Recreate your original MX records, along with any SPF, DKIM and DMARC TXT records, at the new DNS provider.

How long does DNS propagation really take?

Changes apply immediately at the source. The delay people call propagation is caching, controlled by each record’s TTL value in seconds. Lower the TTL to around 300 seconds before making a change and wait for the old TTL to expire, and the switch will then happen in minutes rather than a day or two.

How do I check who owns my domain name?

Run a WHOIS lookup and check the registrant, which is the legal holder, rather than the admin or technical contact. If privacy protection hides it, log into the registrar account directly. If you cannot log in yourself, the domain is probably not under your control, which is worth fixing while relations with whoever set it up are still good.

What is an EPP or auth code?

It is an authorisation code issued by your current registrar that proves you are entitled to move a domain elsewhere. You request it from the losing registrar and give it to the gaining one. A 60-day transfer lock commonly applies after a change of registrant, and some registrars allow you to opt out of it if you ask before making the change.

Does web hosting affect SEO?

Indirectly but genuinely. Hosting determines your time to first byte, the delay before the server sends anything, and page speed is a ranking signal. Server location also adds physical latency for distant visitors. No caching plugin or image optimisation fixes a slow server underneath.

What happens if my domain expires?

Your website and your email both stop, since both depend on the name resolving. There is normally a grace period in which you can renew at extra cost, followed by a redemption period, after which the name is released for anyone to register. Enable auto-renew and keep a valid card and a contact email that does not use the domain itself.