This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 45%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
We have been trying to activate HTTPS on our cdn01.ourdomain.com CDN custom domain in our azure account, but it seems to be stuck on Domain validation for over 24 hours now. We have both direct and cdnverify CNAME records created. We've not received any approval emails either.
Hello @John Carew ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
Could you please let me know if you are using CDN managed certificate or your own certificate to enable HTTPS?
Also, if you have already mapped your permanent custom domain to your CDN endpoint via a CNAME record entry, please delete the temporary "cdnverify" subdomain CNAME record.
As mentioned in our official document,
When you added a custom domain to your endpoint, you created a CNAME record in the DNS domain registrar mapped to your CDN endpoint hostname. If that CNAME record still exists and doesn't contain the cdnverify subdomain, the DigiCert CA uses it to automatically validate ownership of your custom domain.
Regards,
Gita
It is using CDN managed certificate. Just removed the cdnverify record. Still not created. FYI, we tried creating the first time without the cdnverify, still nothing after 24 hours.
Hello @John Carew ,
Thank you for sharing the details.
As mentioned in this doc, automatic validation typically takes a few hours. If you don’t see your domain validated in 24 hours, open a support ticket. Hence, if you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support.
Regards,
Gita
After 72 hours of just waiting, it finally completed. Since we made no change, I can only assume this was an issue with the service that someone in the backend corrected.
Thank you for the update, @John Carew .
Glad to hear that your CDN custom domain is now validated. It could be a lag in the DNS or certificate validation.
Feel free to let me know if you need further assistance on this issue.
Regards,
Gita