Unable to verify domain via DNS

[Patrick Stepkowski]

Hi everyone,

I have added the TXT value to the existing TXT record of my primary domain on Monday but I'm still unable to verify the domain through Atlassian, as I'm receiving unable to verify domain error.

I have tested the record in Route 53 and it comes back fine, it has the required value and the TTL is set to 86400. I have double checked using mxtoolbox and that is also picking up the entry in TXT, so I'm led to believe the issue is somewhat related to Atlassian/our setup. The SSL certificate is also valid.

We have previously verified the domain via HTTPS and are managing the accounts this way, however DNS verification is required to use custom domain when sending email responses from JIRA. Could it be that I need to remove the HTTPS verification first and then verify via DNS? (i.e. JIRA thinks the domain has already been verified and therefore is unable to verify the same domain twice?)

I didn't want to remove the HTTPS record as all our accounts are managed this way, so ideally would like to verify via DNS first, then remove the HTTPS verification.

[Patrick Stepkowski · Accepted solution]

I have solved it by removing the HTTPS record and then verifying through DNS. All working now.