Verify Email Domain Configuration - DKIM

[Zowie Stenroos]

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!

[Veera · Accepted solution]

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.

[Zowie Stenroos]

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

[Veera]

@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.

[Stephan Shere]

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 :)

[Atomic Crayon]

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?