question

SakthiAnandN-0139 avatar image
0 Votes"
SakthiAnandN-0139 asked SakthiAnandN-0139 answered

Unable to map custom domain name to CDN endpoint

Hi there, I created a DNS zone for a subdomain comms.XXXXXX.com and added those NS records to the root domain I have in AWS. I want this subdomain to be mapped to CDN endpoint. I created a CNAME record set (ui.comms.XXXXXX.com) to points to my CDN endpoint resource created in the different resource group. But while mapping the custom domain name, I get the following error:

141591-custom-domain-error.png

DNS zone records:

141601-dns-zone-1.png



I even tried to add CNAME records with No alias set and directly pointed to my CDN endpoint. This worked for me last time but still getting the same error while mapping the domain name.

141611-dns-zone-2.png


I even waited for 5 days if there is any propagation issue but still, I couldn't able to map the custom domain name. I don't know the proper way to check CNAME but I checked with https://dnschecker.org/ if the CNAME is propagated. I could see the CDN endpoint.

141566-dns-check.png




azure-dnsazure-cdn
dns-zone-1.png (51.0 KiB)
dns-zone-2.png (11.1 KiB)
dns-check.png (10.5 KiB)
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @SakthiAnandN-0139 ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

The configuration looks correct to me along with the CNAME mapping. This issue requires the collection of backend logs for further investigation, so 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

0 Votes 0 ·

Hello @SakthiAnandN-0139 , any updates on this issue? If not, could you please drop an email as requested in the private message.

0 Votes 0 ·

Hello @GitaraniSharmaMSFT-4262 This issue has been raised to support and it's an issue with how CDN looks up and validates DNS in their recent changes to CDN. Currently, we are waiting for the fix and we have a workaround for this issue with a different DNS name format currently.

0 Votes 0 ·

Thank you for the update @SakthiAnandN-0139. Kindly let us know if you need further assistance on this issue.

1 Vote 1 ·

1 Answer

SakthiAnandN-0139 avatar image
0 Votes"
SakthiAnandN-0139 answered

The way CDN looks up and validates DNS is changed recently. If you have abc.xyz.xxxxx.com, CDN looks for ns records of xxxxx.com and then ns record for xyz.xxxxx.com and then ns records of abc.xyz.xxxxx.com. In this case, it will work fine.

But if you have TLD xxxxx.com and created a subdomain abc.xyz.xxxxx.com and added it CNAME to TLD xxxxx.com, the validation is failing since there is no ns record for xyz.xxxxx.com. This worked well before but fails now. We raised it to support and the team is working on it.

So the solution for now is, either you need to create a subdomain for each level or have to change the format as we did abc-xyz.xxxxx.com

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.