atlassian unable to verify cname record, even when Mxtool is able too

[Dennis Christensen]

Hi,

Yesterday i setup the DNS recoard for Emails under the organizatio settings and after some time Atlassian was able to verify the recoards.

then over the evening Atlassian is no longer able to verfy the recoards, but looking at mxtoolbox, then it shows the  DNS Record Published are published for all 3 canme record.

Will there be any reason why Atlassian will all the sudden be unable to verify the recoards?

[Arkadiusz Wroblewski · Accepted solution]

Hello @Dennis Christensen 

Failure usually stems from your DNS provider automatically appending the root domain twice (creating a duplicate suffix) or Cloudflare proxying the record, which masks the target destination from Atlassian. The CNAME must be set to "DNS Only."

I recommend running dig -t CNAME on the subdomain in your terminal to verify exactly what is broadcasting. If your dig output matches Atlassian's target perfectly but the status remains unverified, you are likely facing a backend sync glitch. In that case, open a support ticket and provide screenshots of your DNS panel along with the terminal output so they can clear it manually.

If you wouldn't be able to Open Ticket yourself please let me know, but First check things I listed.

[Dennis Christensen]

Hi Arkadiusz,

Thank you very much for your response, but this morning all the CNAME was verfied.

It just confused it that it started with being verfied and then not able to verfied them after some hours and now today they are all verfied again. and i did not change anything.

I will save your response and if i ever have the issue again, i am for sure going to check the dig command you are refering too.

[Arkadiusz Wroblewski]

Sure @Dennis Christensen 

The important thing is that it is working now and you can continue your work.😊