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

Domain verification using TXT record verifies and then supersedes


Hello - I have setup SAML integration to our Atlassian account using Google as an IDP. However, to do this, Atlassian requires to verify domain. 

I added a TXT record as per instructions and it verifies, however, after some time (assuming post TTL propagation), it reverts to a status called SUPERSEDED.

I cannot do a HTTPS verification as I don't have SSL Setup on the domain yet. Also, I understand this can be a DNS related issue, but if anyone has any insight, please let me know how to resolve this.

Domain was purchased on enom(via google) and the NS sits in Route 53 (AWS), where the TXT record has been added along with few other entries. 

1 answer

0 votes
Vasi Atlassian Team Feb 17, 2019

Hey there,

I am not sure if that is going to help much, however I can confirm that in most of the cases "SUPERSEDED" is caused by the fact that continuous check of domain's TXT record is failing for some reason.

Thus, crucial detail here is how you configured TTL of the TXT record. Recommended value is 86400 as per this documentation:

However I would assume that there could be certain scenarios where it should be changed.
Unfortunately I cannot recommend some specific value here, however it could work to try to change it to a higher or lower TTL.

Hope this helps!

Do let me know how it goes and if it was possible to address this case.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events