Problem Definition

Atlassian has a public document that lists Atlassian and third-party domains needed to be part of the network allowlist of customer organisations so Atlassian products can operate successfully. 

• https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/ 

The same document also provides advice on ensuring that the action permits the top-level domain and multiple levels of subdomains.

When allowing a domain, make sure the action permits the top-level domain and multiple levels of subdomains, not just immediate subdomains.

However, some customers with strict network security rules still don't allow top-level domains to be included in their allowlist even with the above public advice shared. Instead, they include specific subdomains as needed on their firewall. 

When these new subdomains are released, some customers experience problems with some functionalities because their firewalls don't allow top-level domains.

Suggested Solution

Provide proactive notification in advance to org and site administrators if Atlassian will be using new domains so the admins can prepare and ensure that their network is ready for the upcoming change.

Workaround

The current advice is to ensure that your network allows the Atlassian and third-party domains listed on this public document.

• https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/