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; } } }

DNS TXT Domain Verification

Michael Arruda_stpfzs

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?

Example:

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

Thanks

Accepted answers

Dave Meyer

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

All comments

Dave Meyer

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

Michael Arruda

@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

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.

Michael Arruda_stpfzs

@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?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

identity-manager

dns

domain-verification