Colin Lee MacLeod — More Better Good
MENU ☰

What Is the Difference Between a Domain and Website Hosting?

A name is not the same as a website

A domain is a registered name, such as example.com. Hosting is the service or infrastructure that makes website content available online. Your website is the content and software people use. These may come in one package, but paying for one item does not necessarily include the others.

DNS records help connect the name to services, which can include a website and email. A domain registrar, DNS provider, web host and email provider can all be different companies. You do not need to change all four just because you want a new design.

Registration means ongoing responsibility

A registrant holds the rights to a registered domain under the applicable agreement. Registration is not a permanent purchase that can be forgotten: renewal, transfer and fee terms matter. Country-code domains have their own operators and rules. See ICANN’s explanation of registration.

Write down which business-controlled account handles renewal and recovery. Give a contractor appropriate access rather than relying entirely on their personal login. Do not put passwords, recovery codes or payment-card details in the ownership worksheet.

Build an account map

Make one row each for domain registration, DNS, website hosting, email, website administration and backups. For every row, record the provider, responsible person, renewal date, cost or billing link, and where the authorized recovery process is documented. Mark unknown items as unknown instead of guessing.

Fictional example: a café renews its domain but discovers the old designer controlled the hosting account. The name may still be registered, while the site remains unavailable. Recovering access and checking the service agreement comes before redesigning pages.

Before moving anything

Ask the new provider what it will migrate and what it will not: files, database, uploads, mailboxes, DNS records and certificates may be separate work. Have a verified backup and a rollback plan before changes. Check how email is routed before replacing DNS settings; incorrect changes can affect mail as well as the site.

This is a planning checklist, not instructions to modify DNS blindly. An authorized provider should inspect the actual configuration and explain the proposed changes. If you cannot identify who controls an account, resolve that first.

Further reading

MDN’s web-server introduction explains how servers store or generate content and deliver it to browsers. Use your actual provider agreements for package inclusions, fees and transfer conditions.

Find more CLM Studio website guides.