An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
hi Ankit Khandelwal & thx for sharing urs issue here at Q&A portal,
the cert order got stuck between domain validation and issuance state. If the list page says Pending Issuance but the cert detail says Issued, that’s not normal UI behavior. Rekey can restart validation, so now u may be dealing w/ a fresh validation order instead of the original renewal.
For domain validation, the exact steps depend on the cert type/provider, but usually u need to create the DNS validation record exactly as shown in the cert blade. If the cert covers subdomains or wildcard names, each required hostname/SAN may need its own validation record unless the provider gives one shared record.
Don’t guess the TXT/CNAME record name. Copy it from the certificate validation page. In Azure DNS, make sure u add it in the correct zone. If the cert is for app.contoso.com, the record may need to live in the contoso.com zone or in a delegated app.contoso.com zone, depending on how DNS is split.
nslookup -type=TXT <validation-record-name>
nslookup -type=CNAME <validation-record-name>
or
dig TXT <validation-record-name>
dig CNAME <validation-record-name>
If public DNS doesn’t return the validation value, the CA won’t complete validation, even if Azure portal shows the record internally.
https://learn.microsoft.com/en-us/azure/app-service/configure-ssl-certificate
https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain
https://learn.microsoft.com/en-us/azure/dns/dns-getstarted-portal
If DNS is correct publicly and it’s still stuck, open a support case w/ cert name, thumbprint/order id if shown, domain names/SANs, validation record values, UTC time u added DNS, and screenshots showing Pending Issuance vs Issued. That mismatch prob needs backend cleanup/retry from the cert provider side.
rgds,
Alex
&
If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal
and at my blog https://ctrlaltdel.blog/