No CNAME record detection on Custom Domain

[Michael Weberschläger]

We've correctly entered the CNAME records with our provider, but unfortunately, the status in Atlassian remains 'provisioned'—meaning the CNAME record detection isn't working properly. Does anyone know of a workaround or what else we could configure with the provider to ensure that Atlassian recognizes the entries? We've tried several different URLs multiple times already...

[John Price]

This may help you:

https://confluence.atlassian.com/jirakb/cname-records-remain-unverified-even-when-correct-values-are-added-in-the-domain-provider-page-1271693441.html 

[Allan Potts]

We're facing the same issue with our newly purchased domain for our gym accessories store, where we sell Lifting Belts. Despite correctly entering the CNAME records with our provider, the status in Atlassian remains stuck at provisioned, and the CNAME record detection isn't working as expected. We've tried multiple URLs and re-entered the records several times, but nothing seems to work. We're considering reaching out to our domain provider to ensure there’s nothing on their end causing the issue and using an external DNS checker such as leafdns to verify that the records are set up correctly. If anyone has found a workaround, we'd love to hear it.