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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Change Domain verification method

Japs Almasol
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Mar 21, 2023

Hi All,

What is the most efficient way to change the specified domain verification in Atlassian with the least amount of downtime if any? We are using DNS verification right now and we are experiencing some issues because we cannot create the SPF records for Office 365. The TXT record for Atlassian's domain verification has the same name as the TXT record for O365's SPF, thus we're looking at changing the verification method to HTTPs.

1 answer

0 votes
Riley Venable (Atlas Bench)
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 21, 2023
The most efficient way to change the domain verification in Atlassian is to add the new HTTPs verification method and remove the DNS verification method. This can be done by adding the necessary HTTPs records to your domain provider and updating the Atlassian email domain settings to reflect the change. Once the HTTPs verification method is in place, you should no longer receive emails about DNS record mismatches. There should not be any downtime during this process.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events