Azure CDN endpoint returns 400 invalid hostname

Peter 1

Hello,

First time using an Azure service, not the first time configuring a CDN. About 18 hours ago, I have configured a CDN endpoint for https, a custom domain, configured my DNS and created a SSL cert in Azure. Unfortunately https://msastagingdoc.azureedge.net returns 400 "Invalid hostname". What else do I need to do?

4 answers

suvasara-MSFT 10,001 Reputation points

2020-06-04T11:19:26.41+00:00

Greetings,

Which CDN product have you deployed in your environment? If it is Standard Akamai then Custom domain Https requires direct CNAME to enable. Also, Please note that after the custom domain HTTPS feature is disabled, it can take up to 6-8 hours for it to take effect. I hope it got resolved now. Else, let us know we will provide more insights.

Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Peter 1 Reputation point

2020-06-04T12:46:31.967+00:00

Hello SubhashVasarapu-8577,

It's standard Microsoft. It's not resolved yet, see the provided URL.
Please sign in to rate this answer.
suvasara-MSFT 10,001 Reputation points

2020-06-05T19:38:47.587+00:00

I did dig on the endpoint where I can see the CNAME pointing to msastagingdoc.afd.azureedge.net. Hope you have configured the CNAME correctly.

Dig o/p:
msastagingdoc.azureedge.net. 1800 IN CNAME msastagingdoc.afd.azureedge.net.

I would recommend you to drop a mail at Azcommunity@microsoft.com where we will enable you with one time free support to resolve this issue.
Sign in to comment
Peter 1 Reputation point

2020-06-05T15:35:28.73+00:00

After 4 days I still haven't been able to test the CDN. And getting support is very cumbersome so far.
Please sign in to rate this answer.
Evan Mulawski 1 Reputation point

2020-06-05T15:57:14.747+00:00

What are you using for the origin?

Peter 1 Reputation point

2020-06-05T18:41:24.197+00:00

Hi EvanMulawski,

The origin hostname is <edit>. It's a test site so it may need to spin up when you browse to it. But it's online and accessible.

Evan Mulawski 1 Reputation point

2020-06-05T18:57:04.03+00:00

What type of origin? Custom, app service, etc? Also enable HTTP raw logs in diagnostic settings for the CDN profile to see backend response info.
Sign in to comment
Peter 1 Reputation point

2020-06-06T06:02:44.363+00:00

Yes, CNAME is ok. Thanks for your help, I'm going to give up. It took too long and meanwhile I have tested several other CDNs which work fine. Not sure why Azure is that complex compared to the others. I may look into Azure later if my selected CDN does not work for us in the long run.
Please sign in to rate this answer.
suvasara-MSFT 10,001 Reputation points

2020-06-12T08:14:56.17+00:00

Hello Peter,

If you are still looking for help we are really glad to assist you. Did you get a chance to send a mail to Azcommunity@microsoft.com?

stevemrf 96 Reputation points

2020-11-13T18:28:26.64+00:00

Hi, a bit late but your CNAME isn't ok. Looks like your pointing your CDN endpoint at another CDN endpoint. I don't see how you where able to verify ownership which is required and will give you the correct values for your cname.record during the process.

You need to point your custom domain name eg. www.yourdomainname.com to your CDN endpoint like this

without downtime -

Create a CNAME record entry for your custom domain and complete the fields as shown in the following table (field names may vary):
Source cdnverify.www.yourdomainname.com
Type CNAME
Destination cdnverify.msastagingdoc.azureedge.net

or with downtime if your up and running and don't mind that, use your domain/cdn name without the "cdnverify."

https://learn.microsoft.com/en-us/azure/cdn/cdn-map-content-to-custom-domain?tabs=dns-provider
Sign in to comment