Issue with Domain verification on Azure

Question

Hi Azure Community,

I recently got some emails from GoDaddy regarding domain access verification. They sent me a URL to approve or disapprove the certificate request. This email from GoDaddy is legit. Please see the email that I have attached as a screenshot. I have blurred the sensitive content. I have not approved this request yet.

After that, I went to my Azure portal and checked the App Service certificate. I have a wildcard certificate that needs domain verification. Please see the attached screenshot. You can see that the Certificate Status is pending issuance and the product type is wildcard and it is valid for a year. The good thing is it has not expired yet. It will expire next month

I clicked on the manual verification which requires adding a TXT record with the name @ and value is the Domain verification token. Our company's DNS records are stored in AWS. We already have a @ record which is of the type TXT and there is already a value in there. So I added another value which is the domain verification token. It's already been 24 hrs and I have not been able to do the domain verification and when I checked the Azure portal->App Service certificate, it either said it failed or there was an error. Can't remember now

Please note that we don't have a dedicated GoDaddy account, it's somehow linked with Azure. I had already called GoDaddy and they said Azure is a reseller of Godaddy so it is best to contact Azure for this case. Could you please assist?

Do you think I should approve the request from GoDaddy which I received via email first and then do the TXT record verification on AWS?

Thank you

Answer 1

Hi @Selvin Pudusserry,

It seems like you're facing issues with domine verification for your Azure App Service wildcard certificate.

1. Since GoDaddy already sent you a request for verification, you should approve it first before attempting the TXT record verification. This ensures that GoDaddy will see the certificate request as valid.
2. After approving the request, verify the TXT record you have set up in AWS. As there is an existing TXT record for @, AWS should not block multiple values. Make sure: The name of the TXT record is exactly @ (or your root domain, as handled by AWS). The value contains nothing but the verification token from Azure. If AWS uses more than one TXT record under @, ensure all the values separate and properly formatted.
3. DNS updates may take as much as 48 hours to propagate, but it's usually faster.
4. Use tools such as MXToolbox TXT Lookup to verify whether the TXT record is publicly accessible.
5. Navigate to the Azure portal => App Service Certificates, choose your certificate and click Retry on domain verification.

https://learn.microsoft.com/en-us/azure/app-service/configure-ssl-certificate?tabs=apex%2Crbac%2Cazure-cli#domain-verification
https://mxtoolbox.com/

If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

Let me know if you have any further Queries.