Introduction
Zendesk processes customer support email at scale. Each ticket notification, agent reply, and automated update needs DMARC alignment. This article covers the setup.
Why this topic matters
Zendesk default behavior uses Zendesk-owned send domains. Without configuration, alignment fails for the customer-facing support channel.
Step-by-step approach
- Zendesk admin → Channels → Email → Add address.
- Add your support email (e.g.,
[email protected]). - Zendesk provides DNS records to publish.
- Publish CNAME for DKIM and any SPF/SRS requirements.
- Verify in Zendesk.
DNS records to publish
Zendesk provides:
- CNAME for DKIM at a specific selector.
- SPF include (
include:mail.zendesk.comtypically). - Optional MX delegation if Zendesk handles inbound for support address.
Best practices
- Use a dedicated subdomain for support if separating from primary domain.
- Test DKIM signing with a sample ticket notification.
- Pair with BIMI for visible support-brand signaling.
- Watch SPF lookup count when adding Zendesk.
- Document the configuration.
Recommended next step
For Zendesk-deployed support, configure custom domain authentication this week. Removes default branding; enables DMARC alignment.
FAQ
Does Zendesk support custom DKIM?
Yes — via the add-address flow.
What about Zendesk Chat or Zendesk Sell?
Different products; each has own configuration.
Will this break in-flight tickets?
No — existing tickets continue normally; new ones use the custom domain.
Can I use multiple support addresses?
Yes — each can be authenticated separately.
What about Help Center notifications?
Use the same custom domain configuration; aligns automatically.
Final thoughts
Zendesk + DMARC requires deliberate configuration. Once done, all support flows align with your domain.