Setting Up Your Custom Domain DNS Records (MX, SPF, DKIM, DMARC)

Created by Alice Joynson-Ellis, Modified on Sun, 15 Nov at 7:17 PM by Curtis Hammock

Connecting your custom domain to Purelymail gives you full control over your email addresses. Because Purelymail does not sell domains, you configure these DNS records in your domain registrar or DNS host (such as Cloudflare, Namecheap, Porkbun, NameSilo, or Cosmotown).


Step 1: Add the Domain in Purelymail

  1. Log into the Account Admin portal (purelymail.com/manage/login) and click Domains.
  2. Click Add new domain, enter your domain name (e.g., yourdomain.com), and copy your unique Ownership Record (purelymail_ownership_proof=...).
  3. Add that TXT record to your registrar's DNS dashboard (see Troubleshooting Domain Verification & Ownership Proof TXT Records).

Step 2: Add Required and Recommended Mail DNS Records

Add the following DNS records in your domain registrar's DNS management panel:

Type Name / Host Priority Value / Target Requirement & Purpose
TXT @ (or blank) - purelymail_ownership_proof=<your-token> Required to verify domain ownership
MX @ (or blank) 50 mailserver.purelymail.com. Required to receive incoming mail at Purelymail
TXT @ (or blank) - v=spf1 include:_spf.purelymail.com ~all Required to authorize Purelymail to send for your domain
CNAME purelymail1._domainkey - key1.dkimroot.purelymail.com. Recommended: DKIM Key 1 cryptographic signature
CNAME purelymail2._domainkey - key2.dkimroot.purelymail.com. Recommended: DKIM Key 2 cryptographic signature
CNAME purelymail3._domainkey - key3.dkimroot.purelymail.com. Recommended: DKIM Key 3 cryptographic signature
CNAME _dmarc - dmarcroot.purelymail.com. Recommended: Standard DMARC policy

Optional DNS Records for Automatic Client Setup (Autoconfig & Autodiscover)

If you want desktop and mobile email clients (such as Mozilla Thunderbird, K-9 Mail, FairEmail, and Microsoft Outlook) to detect Purelymail's IMAP/SMTP server settings automatically when users enter their custom domain email address, you can also add these optional records:

Type Name / Host Priority / Weight / Port Value / Target Purpose
CNAME autoconfig - autoconfig.purelymail.com. Mozilla Thunderbird / K-9 Mail / FairEmail autoconfiguration
SRV _autodiscover._tcp Priority 0, Weight 0, Port 443 autodiscover.purelymail.com. Microsoft Outlook Autodiscover

Notes on Registrar Formatting

  • Host / Name: Some registrars require @ for the root domain; others require leaving the Host field blank. (If setting up a subdomain, see Setting Up Email on Subdomains).
  • Multiple SPF Records: Never publish two separate v=spf1 TXT records on the same host. If you already have an SPF record, add include:_spf.purelymail.com into your existing SPF string.
  • Trailing Dots: If your registrar rejects values ending with a trailing period (.purelymail.com.), remove the final dot.
  • Cloudflare Users: Ensure all CNAME records (purelymail1._domainkey, purelymail2._domainkey, purelymail3._domainkey, _dmarc, and autoconfig) are set to DNS Only (gray cloud), not Proxied (orange cloud). For registrar walkthroughs, see Registrar-Specific DNS Guides: Cloudflare, NameSilo, and Cosmotown.

Using Your Own Custom DMARC Record

  • Custom / Third-Party DMARC: You are welcome to publish your own custom DMARC TXT record at _dmarc (for example, to specify your own rua= reporting address or p=quarantine / p=reject policy).
  • DNS Validator Warning: Purelymail's built-in DNS check specifically looks for our default CNAME (dmarcroot.purelymail.com.). If you use a custom DMARC TXT record, our validator may display a warning that Purelymail's default DMARC CNAME was not detected. This is normal and safe: your custom DMARC record remains active globally and will not block sending or receiving.

Step 3: Critical Final Step: Click Save

After publishing your DNS records at your registrar:

  1. Return to the Domains page in the Purelymail Account Admin portal.
  2. Click Check DNS records (when adding a new domain) or Recheck DNS records (when editing an existing domain).
  3. Once your required checks pass, you must click Save.
  4. Clicking Save commits your verified DNS status and DKIM signing configuration to our mail cluster. Skipping the Save button causes outbound emails to fail with SMTP Error (503): "Cannot send mail: check SPF or DKIM records".

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article