Domain Names, DNS and Web Hosting: What’s the Difference?

A domain name is the registered name people type. DNS publishes directions for services using that name. Web hosting stores and runs the website. They work together, but changing one does not necessarily mean changing the others.

A postal analogy,with limits

Think of a domain as a name listed in a directory, DNS as the directions, and hosting as the premises where the work happens. The analogy is imperfect because DNS can direct different services to different places, but it captures the separation.

Your website might use one host, incoming email another provider, and a marketing tool a third. DNS records connect each service to the domain.

What a domain registration provides

Registering a domain gives the registrant the right to use that name for a defined term, subject to the registry's rules. It does not automatically create a website or mailbox.

The registrar is the company through which the registration is managed. Keep its account recovery details current and make sure the business, not a former employee or unknown supplier,can access it.

What DNS does

DNS is a distributed naming system. Common record types include:

A and AAAA: direct a name to an IPv4 or IPv6 address.
CNAME: makes one name an alias of another name.
MX: directs incoming email.
TXT: carries text used for verification and policies such as SPF and DMARC.
NS: identifies the authoritative nameservers for the domain.

Changing nameservers changes which DNS provider publishes the whole zone. Changing one A or CNAME record usually changes only a specific destination. The first action is broader and needs a complete record inventory.

What web hosting does

Hosting supplies the environment that responds when a visitor reaches the website destination in DNS. It may serve static files or run application code and a database.

The host may also sell domains and email, but that is a packaging decision. Each service still has a distinct technical role.

Why changes take time

DNS responses are cached for a period described by their TTL. After a change, some users may receive the old answer until their resolver's cache expires. This is commonly called DNS propagation, although the change is usually about caches expiring rather than one update travelling steadily around the world.

Lowering TTL before a planned change can help, but it must be done early enough for the previous value to expire.

Three common scenarios

Moving the website only: leave the domain registration and email in place; update the necessary web DNS records.

Changing registrar only: transfer domain management while keeping the same nameservers and service destinations.

Moving everything: transfer the domain, copy the website and migrate email. This creates more dependencies and should normally be staged rather than improvised.

The control checklist

Record the registrar, registrant contact, renewal date, DNS provider, web host and email provider. Note who has administrative access and how recovery works. This small document is more valuable than a bundle marketed as “all in one” but controlled by nobody in the business.