nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DMARC DNS record checks continue to fail

Werner van der Walt_g5xqcz

Hi,

I am trying to setup JSM to send replies using an email from my domain. I followed the steps as descirbed in https://community.atlassian.com/t5/Jira-Service-Management-articles/Doing-Jira-Service-Management-Customer-Notifications-Right/ba-p/1877664 and other articles.

The DMARC records was added to our DNS. I added an _dmarc TXT records as well, as it was originally missing. As a starting point the _dmarc record action is set to none.

It is now more than 48h and the Atlassian Admin DNS record checks are continuing to fail.

Looking at MXToolbox I can confirm the _dmarc record is visible. Can also see the TXT record added. The CName records are not shown.

(DNS is hosted with GoDaddy)

How can I find out what the problem is and why the DNS record checks are failing and what to do to get it working?

Accepted answers

All comments

Paul Wiggers

DNS is always hard to solve but let's give it a go

Have you copy / pasted all the records from your JSM instance into GoDaddy?
Is everything failing or just some checks?
Do you mind sharing your domainname so I can compare those settings to our domain?
DMARC is not required for the custom domain usage in Atlassian. However, it is still a good idea to set it up.

Werner van der Walt_g5xqcz

Hi @Paul Wiggers,

1. Yes, I did. Verified it a second time as well.

2. All items are marked as failed

3. mavensysworx.com

4. Noted.

I logged a similar query at GoDaddy as well to get feedback from there, should it be more an issue on their side. Feedback that I got is that it might be related to JSD Notification were not sent out due to failed DMARC/Marked as SPAM. Add option to control the Reply-To: header in Jira Cloud.

This ticket is however closed, even though the request was to upvote it and watch it.

Paul Wiggers

Thanks for that, it currently looks like you are missing the atlassian entry for your SPF record.

Please add " include:_spf.atlassian.net" unto your current record. Right now it only allows secureservice.net

This would mean that your SPF record should look like:

 v=spf1 include:secureserver.net include:_spf.atlassian.net -all

Werner van der Walt_g5xqcz

The record was updated. Sadly still having the same situation.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management