Authentication entries in DNS must be made on the desired sender domain. If you are mailing from @mydomain.com then entries must be made on the mydomain.com zone. If you are using a subdomain such as @em.mydomain.com the entries must be made on the subdomain level for em.mydomain.com. It is highly recommended to use a domain other than your main corporate email domain (a subdomain of your main corporate domain is sufficient).

Please make the following entries on your desired sender domain. We have used mydomain.com as being an example of the sender domain.

Create a sub-domain with an extension em as given below, or any other extension desired (change instructions accordingly).

em.mydomain.com

Once the subdomain is created there are 3 different types of DNS changes which are required to be configured. These configurations would help to maintain good reputation of your domain and also to ensure that your emails are landing in Inbox.

Type 1: Setting up DKIM record

Type 2: Setting up SPF record for your sender domain

Type 3: Setting up a custom envelope record to handle bounces.

=====================================

Type 1: Setting up DKIM record (Domain Key Policy Record)

Domain Key Identified Mail. It is a method to validate the authenticity of email messages. Incorporating SPF & DKIM into your DNS settings help you to improve your email delivery.

Please create a subdomain as ppdkim._domainkey.em.mydomain.com and add below entry in the zone file of your DNS server,

ppdkim._domainkey.em.mydomain.com.    IN     CNAME          ppdkim.366.io

Once the above entry is made and propagates, please run the following test to verify that the entry has been correctly made:

DKIM Signature TesterURL: http://dkimcore.org/tools/dkimrecordcheck.html
Input
Selector Field: ppdkim
Domain Name: em.mydomain.com

Result should look like the below:

For more information on DKIM Entries visit: http://en.wikipedia.org/wiki/DKIM

Type 2: Setting up SPF record for your sender domain (Sender Policy Framework (SPF) Entries)

If you already have an SPF record change required as follows:

For Ex: If your current TXT record is as given below,

v=spf1 a mx mx:mydomain.com a:mydomain.com -all 

Please change the same to as given below,

v=spf1 a mx mx:mydomain.com a:mydomain.com include: ppspf.366.io-all

If you do not already have SPF entries on your sender domain/s, please make the following entry:

v=spf1 include:ppspf.366.io ~all

Once the above entry is made and propagates, please run the following test to verify that the entry has been correctly made:

SPF Record Tester URL: http://www.vamsoft.com/spfcheck.asp  
Input
IP: 103.52.180.10
Sender email: something@em.mydomain.com

Once done, Click on Show/Hide Log

Result should look like below: SPF policy evaluation finished with SPF Pass. (This is at the end of the Log)

For more information on SPF Entries visit: http://en.wikipedia.org/wiki/Sender_Policy_Framework 

Type 3: Setting up a custom envelope record to handle bounces(Bounce Handling and Catch All)

 It is important to handle the bounces so as to maintain good reputation of your emails and also to ensure that most of your emails land in to Inbox on top ESP’s like Gmail, Yahoo outlook. Etc. The following CNAME entries need to be made on your DNS zone file to ensure that we are able to track bounces on behalf of your sender domain.

 delivery.em.mydomain.com      IN     CNAME       ppspf.366.io

 

After Successful Implementation and Verification

Please return to 366 Degrees and navigate to Portal Admin > Email Administration > Manage Domain. Select the check box and enter the domain you just configured in your DNS. 

(i.e., "em.mydomain.com")

Recommended Best Practices for warming up Domain Reputation

Support

For Questions regarding this implementation document please contact support@366.io

Additionally you can visit our marketplace in 366 Degrees and purchase custom email domain assistance if required.

Did this answer your question?