How to Set Up Zoho Workplace DNS on Cloudflare: Step-by-Step Guide

Woman presenting Zoho Workplace DNS on Cloudflare in a modern office.

Zoho Workplace DNS on Cloudflare: Fast, Reliable, and Secure Email Configuration

If you’ve ever tried connecting your Zoho Workplace email and kept getting “domain verification failed” or saw your messages vanish into spam folders, you’re not alone. Most issues stem from DNS configuration, especially when Cloudflare is involved.

The good news? Setting up Zoho Workplace DNS on Cloudflare the right way takes less than 30 minutes once you know the correct sequence. In this guide, we’ll walk you through every step—from verifying your domain to setting up SPF, DKIM, and DMARC—so your business email runs smoothly and securely.

At PlanetWeb Solutions, we assist Nigerian businesses in configuring Zoho Workplace on a daily basis. What follows is the same process we use to get our clients up and running with reliable, authenticated email.

If you’re new to Zoho Workplace, check out our Zoho Workplace Solutions page to learn more about what it offers for Nigerian businesses.

Why Use Cloudflare for Zoho DNS?

Cloudflare makes DNS management easier than most domain registrars. Changes propagate faster (usually within 10 minutes instead of hours), the dashboard is cleaner, and you get free security features like DDoS protection and SSL certificates.

For businesses in Nigeria, there’s another benefit: Cloudflare’s DNS resolves quickly even when local ISPs have aggressive caching. This means your domain changes take effect faster and more reliably.

🇳🇬 Nigeria Tech Tip:
If you use local registrars like Whogohost or Upperlink, DNS changes can take several hours to propagate. Cloudflare bypasses that lag, which is why many Nigerian businesses prefer it for faster verification and updates. If a registrar’s nameservers are still active while you’re moving to Cloudflare, propagation can be inconsistent. Ensure your domain is fully delegated to Cloudflare nameservers before verification. Double-check your domain’s NS records point only to Cloudflare before verifying in Zoho.

What You’ll Need Before Starting

Make sure you have:

  • Your domain already pointing to Cloudflare nameservers (if not, add it to Cloudflare first)
  • Admin access to your Zoho Workplace account
  • Admin access to your Cloudflare account
  • About 30 minutes to complete the setup

Quick wins before you start:
Set TTL to 300 seconds while configuring. Remove any old MX records from previous providers. Keep a notepad of every DNS change so you can roll back if needed.

Step 1: Verify Your Domain in Zoho

First, you need to prove to Zoho that you own the domain.

  1. Log in to your Zoho Workplace Admin Console
  2. Go to Domains and click Add Domain
  3. Enter your domain name and click Add
  4. Zoho will show you a TXT record for verification. It looks something like:
    zoho-verification=zmverify.xxxxxxxxxxxxxxxxx
    
  5. Keep this tab open. You’ll need to add this to Cloudflare.

Now switch to Cloudflare:

  1. Log in to your Cloudflare dashboard
  2. Select your domain
  3. Click DNS in the left menu
  4. Click Add record
  5. Set up the record:
    • Type: TXT
    • Name: @ (or leave it as your domain)
    • Content: Paste the entire verification string from Zoho
    • TTL: Auto
  6. Click Save

Wait about 5-10 minutes, then return to Zoho and click ‘Verify’.

If verification fails: Double-check that you copied the entire TXT value correctly. These strings are long and easy to mistype. Wait another 10 minutes and try again. You can also check if the record is live using MXToolbox.

Step 2: Add MX Records for Email Routing

MX records instruct other email servers on where to direct mail for your domain. You need to add three Zoho MX records in the correct priority order.

In Cloudflare DNS, add these three records:

TypeNameMail serverPriorityProxy status
MX@mx.zoho.com10N/A (MX not proxied)
MX@mx2.zoho.com20N/A (MX not proxied)
MX@mx3.zoho.com50N/A (MX not proxied)

Important: Cloudflare never proxies MX records. If you have any A, AAAA, or CNAME records for mail-related hosts (like mail, smtp, imap, or webmail), set those to DNS only. For Zoho’s hosted MX values shown here, no proxy setting is needed.

For each record:

  1. Click Add record
  2. Select MX as the type
  3. Leave Name as @
  4. Enter the mail server (mx.zoho.com, mx2.zoho.com, or mx3.zoho.com)
  5. Set the priority (10, 20, or 50)
  6. Make sure the cloud icon is grey, not orange
  7. Click Save

Repeat for all three MX records.

Delete any old MX records from previous email providers. Having multiple MX records from different providers will cause delivery problems.

With your Zoho Workplace DNS on Cloudflare properly configured for email routing, the next step is to set up authentication.

Step 3: Configure SPF and DKIM for Email Authentication

These two records demonstrate that emails from your domain are legitimate, which helps keep them out of spam folders. For a deeper look at email authentication and deliverability, see our Zoho Mail Setup Guide.

Add Your SPF Record

SPF (Sender Policy Framework) informs receiving servers which mail servers are authorized to send email on behalf of your domain.

In Cloudflare:

  1. Click Add record
  2. Type: TXT
  3. Name: @ (or your domain)
  4. Content: v=spf1 include:zoho.com ~all
  5. Proxy status: DNS only (grey cloud)
  6. Click Save

Note: Use include:zoho.com for the US data center. If your Zoho account is in the EU, use include:zoho.eu. If your account is in India, use include:zoho.in.

Important: You can only have one SPF record per domain. If you also use other services that send email on your behalf (like Mailchimp or a CRM), you’ll need to combine them into a single SPF record. Zoho has documentation on how to do this.

Add Your DKIM Record

DKIM (DomainKeys Identified Mail) adds a digital signature to your emails, allowing recipients to verify that they haven’t been tampered with.

First, generate your DKIM key in Zoho:

  1. In Zoho Admin Console, go to Email ConfigurationDKIM
  2. Click Generate DKIM Key
  3. Zoho will show you two pieces of information:
    • A selector name (usually looks like 1518255965._domainkey)
    • A long TXT value starting with v=DKIM1;

Now add it to Cloudflare:

  1. Click Add record
  2. Type: TXT
  3. Name: Paste the selector name from Zoho
  4. Content: Paste the entire DKIM value from Zoho
  5. Proxy status: DNS only (grey cloud)
  6. Click Save

Wait a few minutes, then return to Zoho and click ‘Verify DKIM’.

Step 4: Test Your Zoho Workplace DNS on Cloudflare

Don’t assume everything worked. Here’s how to verify:

Check Your DNS Records

Use MXToolbox to verify your records are set up correctly:

If you’re setting up DNS records as part of a migration, read our How to Migrate to Zoho Mail guide to ensure your messages and data move safely before testing.

Send a Test Email

  1. Log into Zoho Mail
  2. Send a test email to a Gmail or Outlook address you control
  3. Check that it arrives (check spam folder too)
  4. In Gmail, click the three dots next to Reply and select Show original
  5. Look for:
    • SPF: PASS
    • DKIM: PASS

If both show PASS, you’re all set. If either shows FAIL, go back and check those DNS records in Cloudflare.

Optional: Add DMARC for Extra Protection

DMARC (Domain-based Message Authentication, Reporting, and Conformance) instructs receiving servers on how to handle SPF or DKIM checks that fail. It also gives you reports about who’s sending emails claiming to be from your domain.

Start with a monitoring-only policy:

  1. In Cloudflare, click Add record
  2. Type: TXT
  3. Name: _dmarc
  4. Content: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
  5. Click Save

Replace dmarc-reports@yourdomain.com with an actual email address where you want to receive reports.

The p=none policy means “monitor but don’t reject anything.” Once you’re confident everything is working correctly, you can tighten this to p=quarantine (send failures to spam) or p=reject (block failures entirely).

# Move to quarantine later
v=DMARC1; p=quarantine; pct=50; rua=mailto:dmarc-reports@yourdomain.com

# Go strict when everything is stable
v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com

Common Issues When Setting Up Zoho Workplace DNS on Cloudflare

ProblemLikely CauseFix
Domain verification failsTXT record has a typo or hasn’t propagatedCheck the record in Cloudflare for typos. Wait 15 minutes and retry. Use MXToolbox to verify the TXT record exists.
Emails aren’t arrivingMX records are misconfiguredEnsure MX records are added correctly with proper priorities. Wait 10 minutes and test again.
Emails go to spamSPF or DKIM not set up correctlyVerify both records exist in Cloudflare. Send a test email to Gmail and check the headers.
SPF check failsMultiple SPF records or syntax errorYou can only have one SPF record. Combine multiple services into one record.
DKIM check failsWrong selector name or missing quotes in valueRe-copy the DKIM record from Zoho Admin Console. Make sure you copied the entire value.
DMARC fails while SPF and DKIM passDMARC record name or syntax is wrongName must be _dmarc at the root. Recreate the TXT with a simple value first, then tighten.
SPF still soft-fails after adding another senderYou created a second SPF recordMerge all senders into one SPF record. Only one SPF TXT per domain is valid.

For more detailed troubleshooting, we’ll publish a separate guide on solving Zoho DNS problems.

What We Do at PlanetWeb

We regularly configure Zoho Workplace DNS on Cloudflare for Nigerian businesses. The technical process is the same regardless of location, but we also handle:

  • Testing deliverability across different email providers
  • Configuring mobile access policies
  • Setting up email aliases and forwarding rules
  • Ongoing monitoring and support

You can also explore our detailed articles on Zoho Workplace Deployment in Nigeria and Common Zoho Workplace Deployment Mistakes to learn from real-world implementations.

We’re a Zoho Value Added Reseller in Nigeria and can handle configuration, verification, and deliverability checks for you. Get in touch, and we’ll take care of the setup.

Frequently Asked Questions About Zoho Workplace DNS on Cloudflare

Here are answers to some common questions about setting up Zoho Workplace DNS with Cloudflare.

How long does DNS propagation take on Cloudflare?
Usually 5-15 minutes, sometimes faster. Much quicker than traditional domain registrars.
Can I proxy my MX records through Cloudflare's CDN?
No. Cloudflare doesn’t proxy MX records. If you use mail-related A, AAAA, or CNAME records, make sure those are DNS only.
What if my domain verification keeps failing?
Check the TXT record for typos—these verification strings are long and easy to copy incorrectly. Make sure you waited at least 10-15 minutes after adding the record. Try using MXToolbox to verify the TXT record is visible publicly.
Do I need to set up DMARC right away?
No, it’s optional. SPF and DKIM are the essential ones for deliverability. DMARC adds an extra layer of protection and gives you visibility into who’s sending email from your domain. Start with a monitoring policy (p=none) if you decide to add it.
What happens if I have old MX records from another email provider?
Delete them. Having MX records pointing to multiple email providers will cause delivery issues. Your domain should only have the three Zoho MX records listed in this guide.
Share this article:

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top