Configuring JIRA cloud to send emails

Gaynor Mccabe May 17, 2017

Hi,

I have recently received an email asking us to configure some SPF & DKIM records in order to continue to send emails using a custom project email address.

https://confluence.atlassian.com/adminjiracloud/configuring-jira-cloud-to-send-emails-on-behalf-of-your-domain-900996548.html

My query is around the DKIM record, the notes say:

Configure your domain's DKIM records
Setting this up will ensure that JIRA is correctly authorised to send mail from your domain using its email delivery provider. 

    1
s1._domainkey IN CNAME s1._domainkey.atlassian.net.
2
s2._domainkey IN CNAME s2._domainkey.atlassian.net.

Do I set this as a CNAME record with no DKIM record for s2._domainkey.atlassian.net. & s1._domainkey.atlassian.net. ?

Regards.

4 answers

0 votes
Bibi October 1, 2021

It works on Cloudflare using CNAME records instead 

imagen_2021-10-01_154657.png

MicrosoftTeams-image (1).png

0 votes
Julio Cesar Culebro Gonzalez June 27, 2017

Hi I can't add CNAME records like you told us in my CPANEL.

When I add a record like you told us:
     Content = s1._domainkey.atlassian.net

I receive following error:

"Invalid DNS Record: CNAMEs must point a FQDN (Fully Qualified Domain Name)"

Cpanel only leave me add like this one:
Name: s1._domainkey.[my domain]
Type: CNAME
Content: s1.atlassian.net


or like this one:

Name: s1._domainkey.[my domain]
Type: CNAME
Content: s1.[my domain].atlassian.net

But those values doesn't work, I used your validator: https://domain-check.atlassian.io/


I contacted my Hosting provider to ask for he change manually to the "right" value but he told me this:

-------------------
Dear Client,

We apologize for the inconvenience.

It is not possible to set these records.

As the error is reporting the record value should be Fully Qualified Domain Name.
-------------------

What can I do?

Reuben Fergusson July 8, 2018

Im having the same issue. Did you manage to resolve it? 

NGIS Support July 29, 2018

I'm having the same problem also.... with my DNS hosting company was there any resolution to this?

Reuben Fergusson July 29, 2018

I did manage to resolve it. However this required that I basically lost my mind with them and told them they had to do it or we would be moving. 
They had to get a developer to add the changes directly to the database. 

NGIS Support July 29, 2018

Thanks for responding Reuben.

Ugh... great..

 So you directly contacted your DNS hosting company?

Reuben Fergusson July 29, 2018

You're welcome,

Yes sorry for not being clear. I contacted my DNS host. Underscores are actually a part of the standard so they cant really say its not supported. 

NGIS Support July 29, 2018

Hmm it's rather strange I wonder why they said it's not supported or why it's the way it is, either way looks like I'll be contacting my DNS hosting provider.

Thanks a lot, hopefully this thread will assist someone else aswell in the future.

0 votes
Julio Cesar Culebro Gonzalez June 27, 2017

Hi I can't add CNAME records like you told us in my CPANEL.

When I add a record like you told us:
     Content = s1._domainkey.atlassian.net

I receive following error:

"Invalid DNS Record: CNAMEs must point a FQDN (Fully Qualified Domain Name)"

Cpanel only leave me add like this one:
Name: s1._domainkey.[my domain]
Type: CNAME
Content: s1.atlassian.net


or like this one:

Name: s1._domainkey.[my domain]
Type: CNAME
Content: s1.[my domain].atlassian.net

But those values doesn't work, I used your validator: https://domain-check.atlassian.io/


I contacted my Hosting provider to ask for he change manually to the "right" value but he told me this:

-------------------
Dear Client,

We apologize for the inconvenience.

It is not possible to set these records.

As the error is reporting the record value should be Fully Qualified Domain Name.
-------------------

What can I do?

Mike Tocci August 28, 2019

The CNAME content needs to have a trailing dot (.) like this: 

s1.[my domain].atlassian.net.

0 votes
Michael Lysaght May 17, 2017

You need to create 2 entries in your DNS records with the following details

Name = s1._domainkey.[your domain goes here]

Type= CNAME

Content = s1._domainkey.atlassian.net

and similary for s2

Gaynor Mccabe May 19, 2017

Thank you 

Gaynor Mccabe June 20, 2017

I have configured the CNAME records as required but when I verify the domain it is still ssaying I need to add the records.

https://domain-check.atlassian.io/

atlassian verify.PNG

Julio Cesar Culebro Gonzalez June 21, 2017

-

Doug Ticson July 6, 2017

I'm having the same issue using Google Domain / Enom.  Can't get any config to work with their checker.

Suggest an answer

Log in or Sign up to answer