Required DNS records for email
When you add a domain in Settings → Email, Atender generates a list of DNS records that you must add at your DNS provider. The exact hostnames and values are unique to your domain — copy them from the domain row in Atender, do not invent them.
This article explains what each record type is for, so you understand what you’re adding and why.
What gets generated
Atender generates three categories of records:
- MX — One or two — Tells the internet where to deliver mail addressed to your domain
- CNAME — One or more — Routes tracking and authentication paths to Mailgun
- TXT — Two or more — Carries SPF and DKIM data that prove you authorized Mailgun to send for your domain
Add every CNAME and TXT record Atender lists. Add the MX records only when the domain is set to They come straight to Atender; a domain set to Your own mailbox forwards them keeps its own MX.
MX (Mail Exchanger)
MX records control where inbound mail for your domain goes. When someone sends to support@acme.com, the sending mail server asks DNS “what’s the MX for acme.com?” and delivers the message to that host.
Whether you point MX at Atender depends on the How customer replies reach Atender choice for the domain:
- They come straight to Atender — Point the domain’s
MXrecords at Atender, as generated in the domain row. Mail sent to the domain is delivered directly to Atender. - Your own mailbox forwards them — Keep your existing
MXrecords. Your mailbox forwards customer replies to your Atender inbox address. Do not point the domain’sMXrecords at Atender.
If you choose They come straight to Atender but the domain’s MX still points somewhere else, Atender shows a warning on the domain. Customer replies will not reach Atender until the MX records are updated, or until you switch the domain to Your own mailbox forwards them.
When MX points at Atender, it points your inbound mail at Mailgun’s infrastructure. Mailgun accepts mail only for the addresses Atender is set up to receive on that domain — your active inboxes, the domain’s sender address, the CSAT survey sender, support@, and Atender’s own reply addresses — and forwards it to Atender via an inbound webhook, which creates the conversation in your inbox. Mail to any other address on the domain is refused and bounces back to the sender. Changing MX records alone does not create a catch-all mailbox; create an inbox for every support address customers should use.
If you already use this domain for human mailboxes (Gmail, Microsoft 365, etc.), changing the MX records sends all of the domain’s mail to Mailgun, and mail to those mailboxes will bounce. In that case, either choose Your own mailbox forwards them and keep your existing MX, or use a dedicated subdomain like support.acme.com for your support address, so your main mailboxes are unaffected.
CNAME (Canonical Name)
CNAME records are aliases that point one hostname at another. Atender uses them for:
- Email tracking endpoints — when a recipient opens an email or clicks a link, the request hits a hostname under your domain that aliases to Mailgun. This keeps tracking URLs branded to your domain.
- Authentication paths — some authentication flows require a hostname under your sending domain.
TXT (Text)
TXT records carry verification and authentication data:
- SPF (Sender Policy Framework) — a record that lists which servers are allowed to send mail for your domain. Atender’s
TXTrecord adds Mailgun to that list. Without SPF, many recipients (Gmail, Outlook, etc.) treat mail from your domain as suspicious or junk it outright. - DKIM (DomainKeys Identified Mail) — a record containing a public key. Mailgun signs every outgoing message with the matching private key, and recipients verify the signature using the public key in DNS. This proves the message wasn’t tampered with in transit and wasn’t spoofed by someone else.
Both SPF and DKIM are required for healthy deliverability. Recipient mail servers actively penalize or reject mail from domains without them.
Subdomains
You can use a subdomain like support.acme.com rather than the apex acme.com. Add the records exactly as Atender generates them — they will already be scoped to the subdomain you entered.
A subdomain is often the right choice when:
- You already use the apex domain for human mailboxes and don’t want their mail to bounce.
- You want to keep your transactional sending reputation separate from your marketing sending reputation.