Paul O'Brien everything email Subscribe
Paul O'Brien
Paul O'Brien
· 9 min read

Should Your Email Provider Host Your DNS? Why I Keep Mine on Cloudflare

When you add a domain to a new email provider, it often offers to run your DNS for you. Here is why I keep my DNS on Cloudflare instead, when letting the provider do it is fine and how to move without breaking your email.

Jump to section
  1. Three jobs, often three different companies
  2. Why I keep my DNS on Cloudflare
  3. Cloudflare, your email provider or your registrar: side by side
  4. When letting your email provider run DNS is fine
  5. How to move your DNS to Cloudflare without breaking your email
  6. Frequently asked questions
  7. The bottom line
Where should your DNS live?

When you add your own domain to a new email provider, the setup wizard usually asks the same question: do you want to change your nameservers to us, or keep your DNS where it is and add a few records? It looks like a small technical choice. It isn’t, and my answer is always the same. Keep your DNS on Cloudflare, so you can make changes in real time, whenever you like, without asking anyone.

I’ve been asked this a few times now, so this guide explains why I do it that way, the one case where I think letting your email provider run your DNS is perfectly sensible and how to move your DNS to Cloudflare without your email going quiet. If you’re new to DNS, my guide on why using your own email domain makes sense is a good place to start.

Short answer: keep your DNS with a neutral DNS host such as Cloudflare and add your email provider’s records there. Your domain does more than email, you can change anything in seconds and switching email provider later means swapping a handful of records rather than moving your whole domain. The exception is someone who only uses the domain for email and never wants to touch a DNS record. Letting a provider like Fastmail run the DNS is fine for them, as long as the domain itself is registered somewhere else.

Three jobs, often three different companies

Most of the confusion here comes from three separate jobs that sound similar. It’s worth getting them straight, because the whole question is really about which company does the middle one.

JobWhat it doesWho it might be
RegistrarHolds your registration for the domain name. You renew it every year or so, and this is where you set which nameservers the domain uses.The company you bought the domain from, such as Cloudflare Registrar, Namecheap, IONOS, 123 Reg or Porkbun.
DNS hostRuns the nameservers that answer the question “where does this domain’s email and website live?” This is where your MX, SPF, DKIM, DMARC and website records sit.Often the registrar by default, but it can be anyone: Cloudflare, your web host or your email provider.
Email providerStores your mail and sends it for you. It needs a few records at your DNS host to work.Fastmail, Proton Mail, Google Workspace, Microsoft 365 and so on.

When an email provider asks you to change your nameservers to theirs, it’s asking to become your DNS host as well as your email provider. That’s the decision. If you’re not sure who your DNS host is today, my DNS checker will show you where your nameservers point.

Why I keep my DNS on Cloudflare

All of my domains use Cloudflare for DNS, whichever email provider sits behind them. These are the reasons, roughly in the order I’d put them.

1. I can make changes in real time

This is the big one for me. On Cloudflare, a record I add or change is live on its network in seconds, and I can do it from my phone at any time of day. When I’m testing a new provider, fixing an SPF record or adding a verification code, I don’t want to wait, and I don’t want to find that the setting I need is buried somewhere or not offered at all. Email providers are very good at email. Their DNS pages are usually built to do the email part well and not much else, and that’s fair enough, it’s not their main job.

2. My domain does a lot more than email

It’s easy to think of a domain as “my email address”, but look at the DNS records on any domain that’s been in use for a while and you’ll find all sorts in there:

  • The website, and anything else on a subdomain such as a shop, a blog or a status page.
  • Verification records for Google Search Console, Microsoft, Apple, Bluesky handles and other services that want proof you own the domain.
  • Records for services that send email as you, such as a newsletter tool, an invoicing app or a helpdesk.
  • DMARC reporting addresses, so you can see who’s sending as you.

None of that has anything to do with your email provider. If you hand your nameservers to them, every one of those records has to be recreated in their DNS page, and the next time you add a service you’re doing it in your email provider’s settings, which always feels a bit odd to me.

3. Switching email provider is far easier

This is the one people only find out about when it’s too late. If your DNS is on Cloudflare and you want to move from one email provider to another, the domain doesn’t move at all. You copy your mail across, then swap a handful of records: the MX records, the SPF record and the DKIM records. Everything else stays exactly as it was, and you can switch back just as quickly if something isn’t right.

If your old provider runs your DNS, switching providers is more difficult. You have to recreate every record somewhere new, change the nameservers at your registrar and wait for that to spread, all while you’re also moving your mail. And you can’t cancel the old account until you’re certain the nameserver change has finished, because when that account closes, your DNS goes with it. That’s your website and everything else on the domain, not just your email.

Moving email provider when…What you changeWhat can go wrong
Your DNS is on CloudflareThe MX, SPF and DKIM records for email. Nothing else.A typo in a record, which you can fix in seconds.
Your old email provider runs your DNSEvery record on the domain, recreated somewhere new, then the nameservers at your registrar.A forgotten record breaks your website or a service, the nameserver change takes hours to spread and closing the old account too early takes all your DNS with it.

My guide on how to switch email provider covers the order of things when you do move.

4. It’s free, and it comes with the useful extras

Cloudflare’s DNS is free on its free plan, and you don’t have to move your domain registration to use it. You get DNSSEC, which stops anyone faking your DNS answers, with one click. There’s an audit log that shows who changed what and when, which has saved me more than once when I couldn’t remember why a record was there. And because your DNS is there, you can switch on things like Cloudflare’s free DMARC monitoring and Cloudflare Email Routing, which only work for domains that use Cloudflare DNS.

5. It keeps one company from holding everything

I wrote about this in is your email provider a single point of failure? If one company registers your domain, runs your DNS and holds your email, a single locked account, a billing problem or a falling out with that company can take all three at once. Keeping DNS separate means that if something goes wrong with your email provider, you still control the domain and can point your mail somewhere else the same day.

Cloudflare, your email provider or your registrar: side by side

This is how I’d compare the three common places for DNS to live. It’s my view from running my own domains, not a formula.

Cloudflare DNSYour email provider’s nameserversYour registrar’s DNS
CostFreeUsually included with your email planUsually included with the domain
Speed of changesLive in secondsVaries by providerVaries, some are slow
Email recordsYou add them yourselfSet up for you, DKIM includedYou add them yourself
Website and other recordsFull controlPossible, but you recreate them thereFull control on most
DNSSECOne clickDepends on the providerDepends on the registrar
Change historyAudit logRarelyRarely
Switching email providerSwap a few recordsMove the whole domain’s DNSSwap a few records
Best forAlmost everyone with a website or more than one serviceAn email only domain, for someone who never wants to touch DNSFine if you already like it, but often basic

When letting your email provider run DNS is fine

I don’t think it’s always wrong. If you’re not technical, the domain is only used for email and you never want to see a DNS record in your life, letting a provider like Fastmail run your DNS is a perfectly sensible choice. Fastmail sets up the MX, SPF, DKIM and DMARC records for you and keeps them right, and that takes away the most common way people break their own email. I walk through both options in my Fastmail custom domain setup guide.

Not every provider offers it. Plenty of email services only ever ask you to add records at your existing DNS host, so check what yours supports before you plan around it.

One rule if you do: register the domain somewhere else. Your registrar should be a separate company from your email provider, with auto renew on, a card on file and two factor authentication on the login. That way, if you ever fall out with your email provider or lose access to that account, you can still change the nameservers at your registrar and take your domain with you. And don’t use an address on the same domain as the registrar’s contact email, or the renewal reminders will go to an inbox that may not be working.

How to move your DNS to Cloudflare without breaking your email

If you’ve decided to move, it’s not a big job, but it’s one to do carefully. The aim is that every record you have today exists on Cloudflare before the nameservers change, so nothing notices the move.

  1. Write down your current records. Log in to your current DNS host and export the zone file if it lets you, or take screen grabs of every record. Pay special attention to MX, TXT and any CNAME records with “domainkey” in the name, which are your DKIM keys.
  2. Add your domain to Cloudflare. Create a free account, add your domain and pick the free plan. Cloudflare scans your current DNS and imports what it finds.
  3. Check the import against your list. The scan can only find records it can guess the name of, so DKIM records and anything on an unusual subdomain are often missed. Add anything missing by hand, or import your zone file.
  4. Set mail records to DNS only. Any record used for email, especially DKIM CNAMEs and mail hostnames, should have the grey cloud (DNS only), not the orange one. Proxying is for websites, not email.
  5. Turn off DNSSEC at your old host first if it’s on, and wait for that to take effect. Moving with DNSSEC still on is the most common way to make a domain disappear for a day.
  6. Change the nameservers at your registrar to the two Cloudflare gives you. It usually takes effect within an hour or so, but can take up to a day or two.
  7. Check, then switch on DNSSEC on Cloudflare. Once Cloudflare says the domain is active, send yourself a test email, check your website, then enable DNSSEC and add the record it gives you at your registrar.

Tip: leave the old DNS host’s records alone for a week or so after the move. If anything was missed, you can look up what it used to be. Cloudflare’s own guide to changing your nameservers to Cloudflare has the details for each step.

Frequently asked questions

Will moving my DNS to Cloudflare move my email?

No. Your mail stays with your email provider. Cloudflare just answers the question of where your mail should go, using the same MX records you had before. As long as every record is copied across, nobody sending you email will notice.

Do I have to transfer my domain to Cloudflare?

No. You can keep your domain registered wherever it is and only point the nameservers at Cloudflare. Moving the registration as well is optional, and some people prefer to keep the registrar and the DNS host separate anyway.

Is it really free?

Yes. DNS, DNSSEC and the audit log are all on Cloudflare’s free plan. You only pay if you want the paid website features, which have nothing to do with email.

What if Cloudflare has an outage?

No DNS host is perfect, and Cloudflare has had bad days like everyone else. But its DNS runs from data centres all over the world, and an email provider’s nameservers are no more immune to problems. Sending mail also retries for days, so a short DNS outage delays email rather than losing it. For me, the control I get far outweighs the risk.

Can I still use my email provider’s automatic setup?

Often, yes. Some providers can add their records to Cloudflare for you through a “connect” button, and the rest show you exactly what to copy. It takes a few minutes longer than handing over your nameservers, and you only do it once.

I already use my email provider’s nameservers. Should I move?

If the domain is only used for email and everything works, there’s no rush, just make sure the domain is registered somewhere else. If you have a website on it, or you’re thinking about changing email provider, I’d move the DNS to Cloudflare first, as its own job, before you change anything else.

The bottom line

Your email provider is there to look after your email. Your domain is bigger than that, and it should outlive any one provider you use. Keeping DNS on Cloudflare means you can change anything in real time, add new services without fuss and leave an email provider by swapping a few records rather than moving your whole domain. Unless your domain only does email and you never want to look at it, that’s what I’d do, and it’s what I do on every domain I own.

Sources: Cloudflare: change your nameservers, Cloudflare DNSSEC, Cloudflare audit logs, Fastmail: setting up your domain with nameservers, Fastmail: setting up your domain with MX only.

Note: This guide contains no affiliate links.

Paul O'Brien

Paul O'Brien

I've spent over 25 years working hands-on with email, DNS and cloud infrastructure. I test email providers and privacy tools for real, then tell you what they're good at and where they fall short.

More about me

You're subscribed. New articles come by email, as I publish or every Thursday. Change how often

How often?
Nothing else, and I never share your email. Already subscribed? Sign in

Comments