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
I've verified that the TXT record for atlassian-domain-verification is present with TTL 86400 for my domain, which has its DNS at CloudFlare. It's been there for over a week.
The record shows at https://www.whatsmydns.net/#TXT/atlassian-domain-verification.16w.co
But the domain still won't verify. Because I'm using this domain for a SaaS that I don't have FTP access to, uploading the https file isn't an option.
Any ideas for getting this to validate?
Hey Skip, welcome to the Atlassian Community!
Taking a look at your verification TXT record, I can see there's a misconfiguration based on what the validation is looking for. Looks like you've got the validation key set as a TXT record on a subdomain. The validation tool is looking for the validation record at the primary domain.
In Cloudflare, you'd create the TXT record with the @ symbol as the "Name" field:
Then the full record provided in the Atlassian admin panel will go in the "Value" field in Cloudflare:
Once that new TXT record is in place (on the primary domain itself, using @ as the Name), the validation should pass!