DNS records for Atlassian and Office 365

[Japs Almasol]

Quick one. What records did you set in your DNS registry to validate your Atlassian domain (using DNS verification since HTML verification is not applicable for us) and your Office 365 SPF records? Both of them require the same hostname (either @ or blank) and record type which causes a problem. 

BG: someone in the team deleted the O365 SPF (txt) records to make way for the atlassian verification. Now I am left in making these two work without making the other handicapped.

Need some support and some beer, thanks!

[Oday Rafeh]

@Japs Almasol 

You'll need to create a separate TXT record for each service but combine the SPF records.

Here's how you can set it up:

Atlassian domain verification:

Create a new TXT record with the hostname as "@" or blank and the value provided by Atlassian. It should look like this:

Host: @
Type: TXT
Value: atlassian-domain-verification=<verification_code>

Office 365 SPF record:

Create or update the existing TXT record with the hostname as "@" or blank and the value as the combined SPF record for Office 365 and any other services that require SPF:

Host: @
Type: TXT
Value: v=spf1 include: spf. protection. outlook. com include: example. com -all

Replace "include: example. com" with any other services that require SPF. 

Please don't forget to replace the <verification_code> and any other necessary values with your specific information. Also, note that DNS changes may take some time to propagate, so allow for some time before the changes take effect.

[Japs Almasol]

Good evening. It's not for the SPF of Atlassian, it's for the domain verification bit (DNS verification). The name of the record needed for both Atlassian and O365 is the same, either @ or blank depending on the hosting. I can't create a separate TXT record with the same name as the DNS verification record (TXT) of Atlassian. 

Is HTTPS verification the only way to solve my problem? Read online that Atlassian routinely checks the DNS or HTTPS records to verify the ownership of the domain thus deleting the TXT record for Atlassian is not an option.