How to configure your DNS in Cloudflare
When setting up your domain with Maileroo, one of the most important steps is configuring your DNS records correctly. If you’re using Cloudflare to manage your DNS, you’ll need to add the required records to your Cloudflare dashboard.
The video tutorial will show you the exact steps. This document explains the why behind DNS setup and what to expect during the process.
Why Configure DNS for Maileroo?
Adding Maileroo’s records into Cloudflare is essential for establishing your domain’s trust and ensuring emails are delivered reliably. Proper setup allows you to:
- Authenticate Your Domain
- Records like SPF, DKIM, and DMARC prove that Maileroo is authorized to send on behalf of your domain.
- Boost Deliverability
- With authentication in place, your emails are less likely to end up in spam or junk folders.
- Protect Your Brand
- Prevent spammers from impersonating your domain by ensuring only approved servers can send mail from it.
- Unlock Advanced Features
- Certain records enable tracking, bounce handling, and detailed analytics within Maileroo.
What Happens If DNS Isn’t Set Up?
- Emails may be rejected or blocked by providers like Gmail, Outlook, and Yahoo.
- Your domain reputation may suffer, affecting all future mail delivery.
- Recipients could see messages flagged as “via Maileroo” instead of cleanly showing your domain.
- You may miss out on Maileroo’s enhanced features like branded tracking domains and campaign reports.
DNS Propagation in Cloudflare
Once you add the records in Cloudflare, it can take a few minutes up to 24–48 hours for changes to propagate worldwide. During this window, some recipients may see the updated authentication while others may not. Maileroo will automatically detect and verify the DNS records once propagation is complete.
What You’ll Be Adding in Cloudflare
When Maileroo asks you to configure DNS in Cloudflare, you’ll generally be adding:
- SPF Record – Authorizes Maileroo’s mail servers to send for your domain.
- DKIM Record – Provides a secure digital signature to confirm authenticity.
- DMARC Record – Instructs receiving servers how to treat unauthenticated messages.
- Optional Custom Records – Such as CNAMEs for branded tracking domains or bounce handling.