DNS records for email

How to add DNS records for sending domains

If you wish to make to make CoachingCloud email completely invisible to your customers, you can setup special DNS records which will allow you to send via CoachingCloud’s SMTP server powered by Mandrill.

WARNING : This is technical stuff to help protect you and stop email spoofing. Sender Policy Framework (SPF) is a simple email-validation system. DomainKeys Identified Mail (DKIM) is an email authentication method. These are designed to detect email spoofing by providing a mechanism to allow receiving mail exchangers to check that incoming mail from a domain comes from a host authorised by that domain’s administrators.

To add the SPF and DKIM records for your sending domains, you’ll need to add records of type TXT through your hosting provider, domain registrar, or DNS provider.

SPF Record

If you don’t yet have an SPF record, add one for your domain. At a minimum, the value should be the following if you’re only sending mail through Mandrill for that domain:

v=spf1 include:spf.mandrillapp.com ?all

If you already have a TXT record with SPF information, you’ll need to add Mandrill’s servers to that record by adding include:spf.mandrillapp.com in the record (before the last operator, which is usually ?all, ~all, or -all).

DKIM Record

Add a new TXT record with the name mandrill._domainkey.yourdomain.com (just replace yourdomain.com with the domain you’re setting up).

The value for the record should be one of the options listed below. There are two options because the record contains semicolons, and some DNS providers escape semicolons for you while others require you to do it when setting up the record.

With semicolons escaped:

v=DKIM1\; k=rsa\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB\;

With semicolons unescaped:

v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;

DNS Providers

Here are links and information for Bluehost and Godaddy hosting and DNS providers.

Bluehost
GoDaddy

If your host or DNS provider doesn’t appear here, contact their customer support or help files for more information. Each host may handle the adding or editing of records differently, so your host’s technical support or documentation is the best resource for any limitations or formatting specific to that provide.

Once you have done this please contact us so we can verify your records.

Troubleshooting

After you’ve added the appropriate DNS records, it can take up to 24 hours for the changes to take effect. If there’s an error validating your records, you can view the error details in Mandrill for additional information. There are also some third-party resources you can use to check your records or for other details if needed:

  1. Check the SPF validator here. Enter your domain name in the first text box and click Get SPF Record for a diagnostic of your SPF records.

  2. Check whether your DKIM record is valid using the DKIMCore validator. Enter mandrill as the selector and your domain name.

  3. The SPF validator looks for a TXT record with the appropriate SPF information. If your domain has an SPF type record, it’s best to add a matching TXT record for compatibility.

  4. If you already have an SPF record, edit that record instead of adding a new one. The specs for SPF require that there only be one TXT record with SPF information.

  5. If you’ve added the DKIM record and are still seeing that it’s missing, your DNS provider may require the record be formatted differently. The DKIM record Mandrill provides has semicolons escaped with a backslash, so the record starts with this: v=DKIM1\; k=rsa\; and ends like this: \;

  6. Some DNS providers don’t require semicolons be escaped. If you see issues, try removing the backslashes right before semicolons at the beginning and end of the record.

  7. Some DNS providers take longer than others to publish and push the record. If you’re adding a completely new record, those often validate within 10–15 minutes. Changing records can take longer, but can vary based on your DNS provider and TTL for the record.