Domain vs Email Hosting: Can They Be Separate?
Yes. Your domain is the name. Web hosting serves the website. Email hosting stores mailboxes. They often share one DNS zone — and they can point to three different companies.
That is why you can keep a site on Netlify/WordPress hosting and run you@yourdomain.com on MailShrine.
Real-life example: Page & Pour Café
Ngozi’s café site is on a cheap shared host that “includes email,” but webmail is slow and attachments disappear. She wants MailShrine for mail without moving the website.
Her stack after the change:
| Layer | Provider |
|---|---|
| Domain registration | Namecheap |
| Website (A / CNAME) | Current web host |
| Email (MX + auth TXT) | MailShrine |
Three different products
| Product | Job | Typical DNS |
|---|---|---|
| Domain | Brand name people type | Registrar / nameservers |
| Web hosting | HTML, CMS, app | A / AAAA / CNAME |
| Email hosting | Inboxes & SMTP | MX + SPF/DKIM/DMARC TXT |
| If you change… | Site? | Mail? |
|---|---|---|
| Only A/CNAME for web | Moves | Unchanged if MX untouched |
| Only MX for mail | Unchanged | Moves |
| Nameservers wholesale | Can affect both | Plan carefully |
What you need
| Item | Why |
|---|---|
| Domain login | Edit DNS or nameservers |
| Web host still working | Leave its A/CNAME alone |
| MailShrine account | New MX target |
| 30–60 minutes | Plus DNS wait (timing) |
Step 1: Inventory current DNS
Export or screenshot:
- Existing A / CNAME for
@andwww - Existing MX (cPanel? Google trial?)
- Existing SPF TXT
You will replace mail rows, not the website rows.
Step 2: Add the domain in MailShrine
- Sign in → Business Email → Domains.
- Add
pageandpour.ng. - Copy the MX + TXT values shown.
Do not delete web A records while doing this.
Step 3: Publish mail records only
- Remove old MX that points at the web host’s mail.
- Add MailShrine MX.
- Merge SPF into one TXT.
- Add DKIM + DMARC as shown.
- Start verification.
Cloudflare: grey-cloud for mail records.
Step 4: Prove independence
- Visit the website — still loads.
- Wait for Verified (DNS timing).
- Create mailbox + send/receive test (setup guide).
If the site breaks, you edited an A/CNAME by mistake — restore from screenshot.
Step 5: Turn off unused bundled email
Once MailShrine works, disable the old host’s mailboxes so staff do not log into the wrong webmail.
Ngozi’s split-stack checklist
- Screenshot of pre-change DNSCompleted
- Website A/CNAME left aloneCompleted
- Old MX removed; MailShrine MX addedCompleted
- Single SPF; DKIM + DMARC addedCompleted
- Site still online after saveCompleted
- Mail round-trip OKCompleted
Common mistakes to avoid
- Pointing nameservers at MailShrine when you only needed MX — MailShrine needs mail records, not necessarily to host DNS.
- Leaving two MX providers.
- Orange-cloud proxy on MX.
- Assuming “email included with hosting” is mandatory.
Check your work
- Dig/lookup: A points at web host; MX at MailShrine.
- Website HTTP 200.
- Domain Verified in MailShrine.
- Staff use MailShrine webmail only.
Next steps
Citations & References
- Reference: Google: Email sender guidelines
- Reference: ICANN: What is DNS?
- Reference: Cloudflare Learning Center: What is an MX record?
Written by Marcus T., Business Email Specialist. Marcus designs split stacks: site on one host, mail on another, DNS doing the routing.
