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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am sure this question has been asked millions of times - unfortunately, I still haven't found an answer to my question.
The scenario is simple:
value: "v=spf1 include:spf.protection.outlook.com include:spf.mandrillapp.com include:amazonses.com -all"
In order to verify the domain via DNS, Jira requires a blank txt record with the value of this record set to what they provide you in the verification process. With our current txt record setup, the blank name is for SPF values instead.
Question: How do you verify this domain, when you have a blank txt record set up for SPF?
At this point, you're probably thinking, why not use HTTPS verification instead? The roadblock with this method is that we use a CMS for our domain - example.com that is hosted on Squarespace.
From reading many pages, we cannot create https://example.com/atlassian-domain-verify.html page. We could create https://example.com/atlassian-domain-verify/
Question: How do you verify a domain that's hosted on Squarespace?
I have logged a support ticket on the 23rd of September with Atlassian support and we seem to be going around in circles and delays after delays in getting a response. I think the guy has given up and is waiting for the ticket to just die.
Any help would be GREATLY appreciated :)
You should be able to add another TXT record with @ / blank as the name with your DNS provider.
Leave your spf creds as is and add another TXT record row with the Atlassian recommended value.
If Squarespace is your DNS provider (specifically DNS, doesn't matter if they're your website provider), still same applies, add another TXT record with the recommended value from Atlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.