Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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?

1 answer

0 votes

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:

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

227 views 1 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you