Domain vs. Hosting vs. Email: How Your Business Systems Connect
Your website works, but email stops arriving. Someone suggests “moving the domain.” What, exactly, are they moving?
That question is worth asking before anyone changes a setting. A domain, website hosting, and email can share a company and a bill without being the same service.
One familiar name, several separate jobs
Start with the name customers recognize: example.com. A registrar manages its registration. Your registration has an expiration date and needs renewal; buying the name is not the same as buying a finished website. Cloudflare Registrar, for example, describes registration and renewal as its service.1
Next comes DNS: the set of records that tells other systems where to find services attached to that name. Website hosting is where the website runs or its files are served. Email hosting handles mailboxes and messages.
The useful mental model is not “one box called my website.” It is a name connected to several services.
| Layer | Plain-language job | Information to keep |
|---|---|---|
| Domain registration | Maintain the registration of the name | Registrar, account owner, renewal date |
| Authoritative DNS | Publish the name's service directions | DNS provider, access, record inventory |
| Website hosting | Serve the website | Provider, project, billing, backups |
| Email hosting | Receive and manage business email | Provider, administrator, mailboxes, recovery |
One provider may do several jobs. Several providers may cooperate to do them. Neither arrangement is automatically wrong; what matters is knowing where each responsibility lives.
Read the important directions
You do not need to memorize every record type. Recognizing a few makes a support conversation much less mysterious:
- A and AAAA records connect a name to an IPv4 or IPv6 address.
- CNAME records point one hostname toward another hostname.
- MX records identify mail servers for incoming email.
- TXT records hold text used for purposes such as service verification and email authentication.2
Email also involves SPF, DKIM, and DMARC. Broadly, these help identify authorized senders, verify signed messages, and communicate how receivers should handle authentication failures. They are not interchangeable, and an MX record alone does not configure all of them.2
Use the exact values your email provider supplies. This is not a good place to copy a stranger's example and hope it fits.
The connection, pictured
Simplified diagram. This map shows responsibilities, not the full sequence of an internet connection.
Registrar: registration and renewal.
Related responsibility
Website directions
Direct to:
Website hosting
Pages and apps
Mail directions
Direct to:
Email hosting
Business mailboxes
TXT records also support purposes such as verification and email authentication. MX alone does not configure all email authentication.
A registration transfer does not copy website files or mailboxes.
Changing the website destination does not inherently require moving email. Moving the domain registration does not inherently copy website files or mailboxes. Those are separate migration tasks.
There can still be dependencies. Cloudflare requires domains registered through its Registrar to use Cloudflare nameservers; you cannot select another DNS provider's nameservers while keeping the registration there.3 That restriction concerns DNS hosting, not a requirement to host your website or mailboxes with Cloudflare.
What “move the domain” might mean
Ask the person proposing the move to complete the sentence:
We are changing ___ from ___ to ___. We are keeping ___ unchanged.
They might mean transferring registration between registrars, changing authoritative nameservers, pointing the website to a new host, or migrating the entire bundle. Those changes have different consequences.
For a hypothetical brochure-site redesign, the intended change might be only the website's DNS records. If someone replaces the DNS setup without preserving the mail records, the redesign can become an email problem too. The practical lesson is to inventory the working setup before changing it, not to become afraid of every website update.
Ask for a record-by-record change plan and a way to reverse the change. Keep a protected copy of the current DNS records. Do not publish that inventory casually; it is internal operational information.
Make a one-page ownership map
Write down the four layers from the table. For each, add the provider, the business-controlled administrator, the billing contact, and the recovery method. Record where credentials are stored securely, not the passwords themselves.
If a contractor handles maintenance, include their authorized role. If a recovery email depends on the same domain it is meant to recover, discuss an independent recovery option before you need it.
Then ask whoever manages the systems to confirm the map. “I think our web person has it” is a useful starting clue, but not a completed handoff.
You do not need to operate every layer yourself. You do need enough of the map to know what you are paying for, what will change, and who can put it back.
Explore another question
- Domain Ownership: How to Check Who Controls Your Business Domain
- Before Canceling Business Software: An Exit Checklist
Sources
1. Cloudflare, Registrar overview. Registration and renewal service.
2. Cloudflare, DNS record types. Address, alias, mail, verification, and email-authentication records.
3. Cloudflare, Register a new domain. Nameserver requirement for Registrar domains.