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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,211
Community Members
 
Community Events
176
Community Groups

Verify Email Domain Configuration - DKIM

Hi,

I'm trying to set-up email verification so we can send emails from our domain but I need some help with the set-up of DKIM:
Does it need to be a CNAME or can we use TXT (as it usually is?)

Also, I can't access: 
https://confluence.atlassian.com/adminjiracloud/configuring-jira-cloud-to-send-emails-on-behalf-of-your-domain-900996548.html?_ga=2.193411940.891633084.1580801370-1014103949.1519131998

It just says:

Looks like we’re off the beaten track

They say that all roads, lead to Rome.

But we’ve lost our way, so let’s try going home.

Head to our documentation homepage that does exist.

 

Thank you!

1 answer

1 accepted

0 votes
Answer accepted
Veera Atlassian Team Feb 05, 2020

Hi @Zowie Stenroos 

You need to setup the CNAME records as below to ensure that Jira is correctly authorised to send mail from your domain using Atlassian's email delivery provider.

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

Make sure that you follow the below steps to make it work for you.

# First of all, you need to follow the steps to verify the domain which based on your configuration it still not verified. Follow the steps described in the Domain verification documentation.
# Once this is done, then follow the steps to configure the SPF and DKIM records to your mail server as mentioned in Configuring JIRA Cloud to send emails on behalf of your domain documentation.
# The final step will be to change the project email address in project Notification page, to perform this, the user has to be both "organization-admin" and "site-admin" of the instance to make this change.

Hi @Veera

Thank you for your reply!

I know that in your guide that you want us to use CNAME but I'm asking if we can use a TXT record instead of a CNAME record? Since you usually use a TXT-record for DKIM.
If we can't, why CNAME over TXT? (just curious :) )

 

/Zowie

Like # people like this
Veera Atlassian Team Feb 06, 2020

@Zowie Stenroos 

CNAME is to ensure that Jira is correctly authorised to send mail from your domain using Atlassian's email delivery provider.

Yes, you can use TXT records for DKIM, but it'll not authorise Jira to send mail from your domain using Atlassian email provider.

Like # people like this

Veera, you are correct, however, if you do a test you'll see that everything works correctly!

> nslookup -type=cname s1._domainkey.exqsd.com
Server: cdns1.cox.net
Address: 68.105.28.11

Non-authoritative answer:
s1._domainkey.exqsd.com canonical name = s1._domainkey.atlassian.net

>nslookup -type=txt s1._domainkey.exqsd.com
Server: cdns1.cox.net
Address: 68.105.28.11

Non-authoritative answer:
s1._domainkey.exqsd.com canonical name = s1._domainkey.atlassian.net
s1._domainkey.atlassian.net canonical name = s1.domainkey.u9256.wl007.sendgrid.net
s1.domainkey.u9256.wl007.sendgrid.net text =

"k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDOiBiqCIHTotaDdBPZFWcSEXBRNFbf9od2ZbSzxbMGyj9t2waEv9Nt/povamr8b7BMICyF1rVUz+nNcIwPlrZLGg+YwnWchUal9nK1nj41z7MuZ+xF8MmZjzOKW0XBF+vHRiiKNz0TvXnCTSk+qNEEcutW7xeL61/LoAX59HqmTQIDAQAB"

Perfect :)

I am getting an error and I have the CNAME records set up correctly as noted above:

SPF entry _spf.atlassian.net is missing from configuration

I have two separate CNAME records as noted above.

I also have records in the TXT file as follows based on the documentation:

"atlassian-domain-verification=UTCMu0JNmZg3goaU25Da7A3IDFv9miVXlVEJFHJ7uYZV4zbB05mlzOXWy56nZno4"
"atlassian-sending-domain-verification=b226ec60-9b31-4fe1-977c-3d0ccb30c102"

Are these conflicting? Should I only have the CNAME records in place and delete the TXT records?

Suggest an answer

Log in or Sign up to answer