Domains and DNS records

Darzus sends from a domain you control. To prove that, you add a few records to your domain's DNS. Receiving mail servers check those records. When they pass, your mail is more likely to reach the inbox.

Three kinds of record do the work:

  • DKIM signs each message with a key that your DNS publishes. A receiver can check that the message was not changed in transit.
  • MAIL FROM is a subdomain that Darzus uses for bounces and complaints. Its SPF record is checked there.
  • DMARC tells receivers what to do with mail that fails these checks, and where to send reports.

The records

When you add a domain, the response lists every record to publish, with its exact name and value. Copy them exactly. This table shows what each record is for, using example.com as the domain.

RecordTypeNameRequiredWhat it is for
DKIM key (three records)CNAME<token>._domainkey.example.comYesThe signing key. Each token has its own record.
MAIL FROM mail serverMXsend.example.comYesReceives bounces and complaints for the MAIL FROM subdomain. Priority 10.
MAIL FROM SPFTXTsend.example.comYesThe SPF policy for the MAIL FROM subdomain. Its value is v=spf1 include:amazonses.com ~all.
DMARC policyTXT_dmarc.example.comNo, but recommendedTells receivers how to handle failures and where to send reports

The MAIL FROM subdomain is send followed by your domain, so send.example.com. Darzus sets this name for you, and the domain response shows it as mail_from_domain.

Use the exact values from your domain response. Only the DKIM tokens differ from one domain to the next.

DKIM

DKIM uses three CNAME records. Each one points a name under your domain to a signing key that Amazon SES manages for Darzus. Each name starts with its own token, and the domain response gives you all three.

MAIL FROM on a subdomain

Bounces return to the MAIL FROM subdomain, so SPF can pass for that subdomain while your main domain keeps its own mail settings. Your main domain does not need a new SPF record for Darzus. Keep the one you have. Two SPF records on the same name make the check fail, so never keep two.

DMARC

DMARC is recommended, not required. The record Darzus shows is v=DMARC1; p=none;, which tells receivers to take no action and to report nothing. To receive reports, add a reporting address, such as the one below. Replace example.com and the address with your own:

Type:  TXT
Name:  _dmarc
Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com

p=none tells receivers to report failures without blocking mail. Read the reports for a few weeks. When your real mail passes, move to p=quarantine, and later to p=reject.

Add the records at Namecheap

These steps are for Namecheap's current website. Other registrars have similar screens.

  1. Sign in to Namecheap, open Domain List, and choose Manage next to your domain.
  2. Open the Advanced DNS tab.
  3. Under Host Records, choose Add New Record.
  4. Choose the record type (CNAME, MX or TXT). Enter the host and the value exactly as Darzus shows them. For an MX record, also enter the priority Darzus gives you.
  5. Leave TTL on Automatic.
  6. Repeat for every record, then choose Save All Changes.

Namecheap adds your domain name to each host for you. Enter abc123._domainkey, not abc123._domainkey.example.com. If you enter the full name, the record ends up with the domain twice and never verifies.

Enter TXT values as they are shown, without extra quotation marks.

If your domain already receives mail through Namecheap Email Forwarding or another mail provider, keep those MX records. The MX record for MAIL FROM is on the send subdomain, so it does not replace them.

If your DNS is hosted somewhere other than Namecheap, add the same records there. The steps are the same.

Check the records

Open the domain in the dashboard and choose Verify. Darzus checks each record in DNS, and asks the sending provider whether the domain is ready. You can run the same check with POST /v1/domains/{id}/verify.

Each record shows one of these results:

  • ok: the record is in place
  • missing: Darzus could not find the record
  • mismatch: the record exists, but its value is different from the one Darzus shows
  • unchecked: Darzus has not checked it yet, or the DNS lookup failed

The domain's status becomes verified when DKIM and MAIL FROM are both in place. can_send becomes true when the signing records are verified, which is what live sending needs. A domain can send as soon as can_send is true.

DNS changes can take a while to spread. If a record is missing, wait and verify again.

Subdomains

Mail can come from any subdomain of a verified domain. If example.com is verified, hello@mail.example.com can be sent from as well.

Common problems

  • A record is missing. Look for the domain name typed twice in the host. Check that the value matches exactly, with no extra spaces.
  • A record is mismatch. The value in DNS differs from the one Darzus shows. Copy it again, and remove any old record with the same name.
  • SPF fails. Look for two SPF records on the same name. Keep one.
  • Verified, but mail still goes to spam. Verification shows the records are in place. It does not judge your content or your list. See Deliverability.
  • A live send fails with domain_not_verified. The From address uses a domain that is not verified yet, or its records are not all in place. Finish the records, then verify again.
  • A live send fails with free_email_from. The From address uses a free mail provider. Send from an address on a domain you own.