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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

DNS TXT Domain Verification

Trying to verify a domain with a TXT record, but already have a TXT record for the base domain. If I add a second TXT record will I break the first one?


JIRA Cloud Instance #1 DNS TXT Record: IN TXT atlassian-domain-verification=foo

JIRA Cloud Instance #2 DNS TXT Record: IN TXT atlassian-domain-verification=bar



1 answer

1 accepted

1 vote
Answer accepted

@Michael Arruda is this for a subdomain? You should be able to place a second TXT record for alongside

@Dave Meyer Thanks for your reply. No, it for the base domain. We already have another team with a TXT record, but we need to add one for our separate JIRA cloud subscription. Will there be any issues doing so?

Dave Meyer Atlassian Team Apr 20, 2019

Hi @Michael Arruda, got it. Domains can only be verified for one organization at a time. It's independent of any Jira Cloud subscriptions you might have. Organizations (and domain verification) goes across all Atlassian cloud products and services.

So if Organization A has claimed, all Atlassian accounts with email addresses will be managed by Organization A and Organization A's security policies (like SAML SSO) will apply to all users.

If Organization B adds a separate TXT record that it generates to verify, then the domain claim will be transferred to Organization B. Then all accounts will be managed by Organzation B and Organization B's security policies (like SAML SSO) will apply to all users.

@Dave Meyer Got it. Since the other organization has already claimed the domain, it sounds like we won’t be able to perform domain verification and hence won’t be able to use SAML SSO. This is really unfortunate since we will now have to manage local accounts for several hundred users. Are there any alternative solutions you can suggest?

Dave Meyer Atlassian Team Apr 20, 2019

@Michael Arruda what is preventing the existing organization that has already claimed the domain from configuring SAML SSO?

There's nothing stopping you form claiming the domain and setting up SAML SSO, as long as the other organization is OK with you having control over all accounts on the domain.

@Dave Meyer @Sorry, I misunderstood. So it sounds like the second TXT record is fine as long as organization A is ok with us claiming the domain. The other problem is our company is so big that we don’t know who organization A belongs to. The only way we knew someone else was using it is because of the existing TXT record at Is there a way to figure that out by doing a reverse looking on your end? 

Thanks for the help. 

Dave Meyer Atlassian Team Apr 21, 2019

Hi @Michael Arruda yes, please create a support request and we can help you out.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Access

Resources + Q&A from "What's new in Atlassian Access" webinar

Hi Community! Thank you to all those who joined our What’s new in Atlassian Access webinar last week! We received so many great questions about existing functionality and newly released features of...

1,125 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you