← Build log

How I Finally Untangled My DNS to Host Email Separately While Keeping My Website Elsewhere


Some things are supposed to be simple. Email hosting, for example. And yet, for solo builders, DNS is like the DMV of the internet: everything touches it, nobody enjoys it, and one wrong entry means you’re standing in the wrong line for hours.

I ran into this exact mess when I wanted to set up business email for my project domain: example.com. My website was already happily hosted, my domain was registered, and I didn’t want to move anything. But I did want full email hosting that wouldn’t dump my messages into the spam abyss.

This post is how I finally solved it—and how you can too.


TLDR: The Fast Path for Solo Builders

What You’ll Gain:

  • Full email hosting for your custom domain (e.g. info@example.com)
  • Keep your website deployed wherever you want
  • Keep your domain registration wherever you want
  • Avoid paying for full-stack hosting bundles if you don’t need them
  • Set up in under 60 minutes once you have the DNS records

Bottom Line Value: You don’t have to compromise your deployment stack just to get professional email.


The Problem: Email and DNS Don’t Like Being Friends

If you’re a solo builder:

  • You want to host your site wherever it fits best for your needs.
  • You want to keep your domain registered with a provider you trust.
  • You want professional email (info@example.com), but some email hosting pricing feels unnecessary.

But here’s where things break down: Most email providers assume that if you want email, you’re also hosting your website and DNS with them. When you’re not, their dashboards get weird.


The Approach: Decoupling Web Hosting from Email Hosting

I already had my domain registered and my website hosted. I wanted to add full-featured email hosting without disrupting anything else.

The core idea is this:

  • You don’t need to move your website or DNS.
  • You only need to add your email provider’s email DNS records into your current DNS provider.
  • Your website stays where it is like nothing happened.

The Exact Steps

Step 1: Get Your Email Plan

  • I signed up for a standalone email hosting plan that allows external DNS management (many providers offer this at low cost).
  • This unlocks email hosting even if your DNS and website are external.

Step 2: Collect Your DNS Records

Once you purchase, your email provider gives you a table of records like this (using example.com as our safe, generic domain):

MX Records

TypeHostValuePriorityTTL
MX@mx1.emailprovider.com514400
MX@mx2.emailprovider.com1014400

SPF Record (TXT)

TypeHostValueTTL
TXT@v=spf1 include:_spf.emailprovider.com ~all300

DKIM Records (CNAME)

TypeHostValueTTL
CNAMEemail-a._domainkeyemail-a.dkim.emailprovider.com300
CNAMEemail-b._domainkeyemail-b.dkim.emailprovider.com300
CNAMEemail-c._domainkeyemail-c.dkim.emailprovider.com300

Autoconfig (Optional, but nice)

TypeHostValueTTL
CNAMEautoconfigautoconfig.emailprovider.com300
CNAMEautodiscoverautodiscover.emailprovider.com300

Step 3: Update Your DNS

  • Log into your DNS provider’s control panel.
  • For Mail Settings, switch to Custom MX (if applicable). Enter the MX records as provided.
  • Then manually add the TXT and CNAME records exactly as provided.
  • For any “Host” field, use @ to represent your root domain (example.com). For subdomains (like autoconfig), enter them as-is.

DMARC helps protect against spoofing and phishing. Start with a safe “monitoring only” policy:

TypeHostValueTTL
TXT_dmarcv=DMARC1; p=none; rua=mailto:dmarc@example.com;300

You can later tighten this to p=quarantine or p=reject once you verify your mail is being authenticated correctly.

Step 5: Verify Everything

Use tools like:


The Human Reality: Why This Was So Confusing

The problem isn’t the technical complexity. It’s the assumption baked into most platforms that if you want email, you must want all-in-one hosting too. That’s rarely true for solo builders who are piecing together the best-in-class tools for different jobs.

  • One provider gives you amazing web deployments.
  • Another gives you reliable domain registration.
  • Another gives you full-featured email hosting.

But getting these three services to play nice? That requires you to be the glue. Nobody tells you that upfront.


The Business Impact

  • Saved significant ongoing costs compared to bundled SaaS solutions.
  • Full professional email domain without sacrificing my existing web stack.
  • Zero disruption to my website deployments.
  • Scalable: I can add more mailboxes or aliases as my solo projects grow.

What This Means for Solo Builders

If you’re solo building, you’re probably doing exactly what I am:

  • Picking best-of-breed tools that fit your workflow.
  • Avoiding unnecessary vendor lock-in.
  • Keeping costs lean while maintaining professionalism.

This kind of DNS wrangling may feel annoying, but once you’ve done it once, you unlock a huge amount of flexibility.

You can control your own email infrastructure without being forced into a one-size-fits-all SaaS stack. More importantly: you keep building your projects exactly where they perform best.


Next Steps You Can Take Today

  1. Decide if you want full email hosting or just email forwarding.
  2. Choose an email host that allows external DNS management.
  3. Gather your DNS records.
  4. Update your DNS at your domain registrar.
  5. Verify deliverability with mxtoolbox.

If you’re building like I am, you’re going to bump into these weird seams between SaaS products. The trick is knowing that you can stitch them together—and most importantly, that you don’t need to compromise your stack just to have a working email address.