You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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:
example.com IN TXT atlassian-domain-verification=foo
JIRA Cloud Instance #2 DNS TXT Record:
example.com IN TXT atlassian-domain-verification=bar
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 example.com, all Atlassian accounts with @example.com email addresses will be managed by Organization A and Organization A's security policies (like SAML SSO) will apply to all @example.com users.
If Organization B adds a separate TXT record that it generates to verify example.com, then the domain claim will be transferred to Organization B. Then all @example.com accounts will be managed by Organzation B and Organization B's security policies (like SAML SSO) will apply to all @example.com 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?
@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 example.com. Is there a way to figure that out by doing a reverse looking on your end?
Thanks for the help.