DKIM S1 and S2 can it also be S3 and S4?

[Hanno-Wybren Mook]

Is it posible to set other DKIM records to connect Jira Service Desk in order to use a own email address for responding to tickets?

[Angélica Luz]

Hello @Hanno-Wybren Mook,

Thank you for reaching out to Atlassian Community!

Checking some similar cases, I found out that currently, it's not possible to add a different CNAME for DKIM. 

There is a feature request suggesting the implementation of such ability:

•  add CNAME/alias for DKIM names

Please, click on vote and also watch to receive future updates.

There is a possible workaround that you can try:

Essentially, if you can edit your current s1/s1 DNS records temporarily to different selectors, for example, s5/s6, then add the Atlassian DKIM records, wait for propagation and DNS confirmation on http://domain-check.atlassian.io, then add the custom email notification address. 

You can then alter the Atlassian DKIM records to s3/s4 and revert your s5/s6 records back to the original s1/s2. 

That will allow Atlassian to continue sending emails on your behalf. Presumably, take that to mean we don't periodically poll the DKIM records as opposed to the domain verification records.

If your current s1/s2 selector records are being used for email delivery or something critical obviously, it's recommended making these changes outside of business hours or during a period of low activity.

If possible, the workaround is as follows:

1. Edit current s1/s2 records to use s5/s6, just for the host leave the values as is.
2. Add Atlassian DKIM records on s1/s2 and wait for confirmation on domain-check.atlassian.io.
3. Add custom email notification address.
4. Edit Atlassian DKIM host records to use s3/s4 (the values should still remain s1._domainkey.atlassian.net. & s2).
5. Revert original records from s5/s6 back to s1/s2.

Your original records should be back to how they were and you should find we are still able to send emails on your behalf.

Hope this helps!

Regards,
Angélica