Publish a DMARC record to protect your domain when sending support email through Zendesk.
TXT
_dmarc
v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
Ensure Zendesk SPF and DKIM are configured before enforcing DMARC.
Set up both SPF (include:mail.zendesk.com) and DKIM (zendesk1/zendesk2 CNAME records) before adding DMARC.
Send a test support email from Zendesk and check email headers for SPF and DKIM pass.
Add a TXT record at _dmarc.yourdomain.com.
v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1Review DMARC reports to verify Zendesk emails are passing. Look for any alignment issues.
Move from p=none to p=quarantine and finally p=reject.
After adding your DNS records, use our free DMARC checker to verify everything is configured correctly. DNS changes typically propagate within minutes, but can take up to 48 hours.
Zendesk supports DKIM alignment through its CNAME-based DKIM setup. SPF alignment depends on your email configuration.
If SPF and DKIM are properly configured, no. But if either is missing, enforced DMARC may cause ticket emails to be rejected.
No. One DMARC record per domain covers all email, including Zendesk.