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

dkim failed

이상미 April 23, 2020

It completed domain authentication by adding txt record.
The jira service desk changed the alarm email address.

DKIM validation for this domain has failed. The message goes like this...
What should I do?

1 answer

0 votes
Angélica Luz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 27, 2020

Hello @이상미,

Thanks for reaching out to Community!

I can see that the domain has been verified but on https://domain-check.atlassian.com/ it shows that DKIM records are missing and SPF entry is also missing.

After verifying the domain, in order to change the outgoing email in a Service Desk project, it's necessary to follow the steps of the documentation below:

Please, give it a try and let us know how it goes.

Regards,
Angélica

이상미 April 27, 2020

This message appears.

DKIM the following records are missing s1._domainkey.nkia.co.kr, s2._domainkey.nkia.co.kr from the configuration.

s1._domainkey.nkia.co.kr s2._domainkey.nkia.co.kr
SPF entry _spf.atlassian.net is missing from configuration

------

First, add v=spf1 insert:_spf.atlassian.net ~all records in the domain's spf record configuration.
Second, should I add s1._domainkey.nkia.co.kr, s2._domainkey.nkia.co.kr records as the dkim record configuration for the domain?

Angélica Luz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 28, 2020

Yes, the error message appears because it wasn't configured correctly.

Please, follow the steps of the documentation I sent on my previous answer.

1. Configure your domain in your Atlassian Account

For Jira to send email notifications from your own domain, you'll need to prove ownership of the domain. In order to verify yours please access this article.

2. Configure your domain's SPF records

v=spf1 include:_spf.atlassian.net ~all

3. Configure your domain's DKIM records

s1._domainkey IN CNAME s1._domainkey.atlassian.net.

s2._domainkey IN CNAME s2._domainkey.atlassian.net.

4. Validate that SPF and DKIM configurations are correct

Use https://domain-check.atlassian.com tool to verify that everything has been configured correctly.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events