Submit a ticket My Tickets
Login  Sign up

DKIM Records

What are DKIM (Domain Keys Identified Mail) Records?

    Domain Keys Identified Mail (DKIM) records allow a recipient to validate a sender as the owner of an email message. Domain Keys use public key encryption to apply digital signatures to email, this allows verification of the sender as well as of the integrity of the message in question. DK/DKIM records are generated by your email service provider and entered as TXT Records within Constellix. Visit the Domain Key Public Website to learn more. 

Please note if you have a TXT value that is longer than 255 characters, you will have to split the value into 2 parts using double quotations "". You will have to add both parts as your TXT record value. 

For Example: 

"String One""String Two""String Three"

How to Configure DKIM Records

1.Select Managed DNS and click on Domains

2. Select the Domain Name you want to add an A record too.

3. Under the TXT Records section, click the  plus_icon to add a record.

DKIM Record Fields

A) Name: This will be the hostname for the record, typically a computer or server within your domain. It is important to note, the domain name is automatically appended to the “Name” field of the record. For example, defining in DNS would be creating an A record with the name field of “www” within the domain. If the “Name” field is left blank, it represents the root record of the domain. The root record for the base domain can also be referred to as the apex record and is represented in a @ symbol in some documentation. Typically DKIM records would have a blank name field.

B) TTL: The TTL (Time to Live) in seconds is the length of time the record will cache in resolving name servers and web browsers. The longer the TTL, then remote systems will lookup the DNS record less frequently. Your name servers will also receive less query traffic since most queries are answered by resolving name servers. Conversely, the shorter the TTL the faster any changes you make to your DNS will propagate in servers that have cached data. However, your domain will receive more query traffic.

C) Value: The DKIM string for your domain.

D) Notes: Add a helpful note with keywords so you can search for your records later.

E) Save: Save your record changes and don’t forget to commit your changes after you’re done making record changes for this domain!

Recommended values:

Records that are static and don’t change often should have TTL’s set between 1800 (being on the low end) to 86400 seconds (30 minutes to 1 day cache).

Records configured with Failover or that change often should have TTL’s set anywhere from 180 to 600 (3 to 10 minutes cache).

If a change is needed for a record with a high TTL, then the TTL can be lowered prior to making the change and then raised back up again after the changes were made.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.