Cannot Set Up Naked Domain on Azure CDN RRS feed

  • Question

  • What I am using:

     - Azure CDN: `Premium Verizon`
     - DNS: `DnsMadeEasy`

    I am struggling to setup all endpoints of my domain on Azure CDN; I am able to set up endpoints with a prefix to my domain (i.e `prefix.mydomain.com`) but for the naked domain (`mydomain.com`) it doesn't work.

    I have my CNAME records pointing to the CDN endpoint and for these hostnames it works fine. I am aware that an A record in DNS can only point to an IP, so instead am using DnsMadeEasy's ANAME record to point to the CDN (more info on ANAME https://dnsmadeeasy.com/services/anamerecords/)

    From the error I am seeing it looks like Azure is verifying the custom domain (the hostname I am trying to add) by checking the endpoint which `mydomain.com` is pointing too. Since DnsMadeEasy pre-populates an A record with whatever IP the ANAME resolves too (or at least I think that is what it does) Azure is failing the validation because it is getting the IP of the endpoint, thus not allowing me to add it.

    Has anyone else seen this?

    Is this intended behaviour?

    Has anyone else added a naked domain to Azure CDN?

    Is this a bug in Azure CDN?

    Sunday, July 8, 2018 7:56 PM

All replies

  • It is an expected behavior. Currently we only check CNAME and as naked domain can't use CNAME, we fail the validation. We are working on a solution to support root domain on CDN end to end and as soon as this feature is available, we will allow validation for not just CNAME. Stay tuned.
    Tuesday, July 10, 2018 5:25 PM
  • Any update?
    Sunday, November 11, 2018 4:32 PM
  • Any update on this? Seems like the naked domain are still unsupported by Azure CDN.
    Tuesday, January 22, 2019 12:11 PM
  • A relatively straightforward way to get around this is to verify the domain using the temporary mapping feature, cdnverify.

    Set up a CNAME "cdnverify.<yourdomain>" to "cdnverify.<endpoint>.azureedge.net". Once all is verified and set up (including SSL provisioning if desired), delete the CNAME and use ANAME for the root record.



    Wednesday, February 6, 2019 10:51 AM
  • Thank you, thank you, thank you - your solution is perfect timing for me!

    ...using the temporary mapping feature, cdnverify WORKS to be able to add the naked root to a CDN endpoint! 

    The 8 hour HTTPS activation is happening now and the root domain will finally resolve instead of serving a 404 error. 

    So simple - it was right in front of us & I hadn't tried it. 

    Thursday, March 14, 2019 10:11 PM
  • Hi, what if my DNS provider doesn't have the ANAME record? Is there another workaround?
    Wednesday, September 18, 2019 8:39 PM
  • The answer from theanatoki Doesnt work GoDaddy as there is no ANAME. Any other ideas?

    • Edited by UNsTephenk Monday, November 11, 2019 10:47 PM
    Monday, November 11, 2019 10:46 PM
  • I also currently have GoDaddy for my DNS provider, after running through the workaround process of using the CDNVerify prefix to add the custom domain I then set my A-Record in GoDaddy to the IP address of my Azure CDN's Hostname. 

    I can now hit my site without providing a subdomain prefix, however if the IP address changes it would stop working. Not a valid production site fix. My purposes currently are for testing/dev so its not a big deal, but i will have to move to another DNS provider that allows for AName redirection or hopefully use whatever solution Microsoft implements once i am ready to take my project live.

    Tuesday, February 25, 2020 1:32 AM
  • were you able to enable custom HTTPS? im getting an error saying "enabling Https with CDN managed cerificate is not supported anymore for apex (root) domains"

    Tuesday, February 25, 2020 7:26 PM