Azure-docs: Confusion on "Verify the custom domain" section

[zhalu]

In "Verify the custom domain" section, the example uses URL "http://cdn.contoso.com/my-public-container/my-file.jpg". Maybe I do not understand it correctly, should it use "http://cdnverify.www.contoso.com/my-public-container/my-file.jpg" instead? It looks confusing to me, can it clarify a bit more clearly?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b32fbbf3-178d-a0ef-7c3a-87df74a8eb16
• Version Independent ID: 2475b34a-88e8-5b45-723d-ee0a62230b8a
• Content: Tutorial - Add a custom domain to your Azure CDN endpoint
• Content Source: articles/cdn/cdn-map-content-to-custom-domain.md
• Service: cdn
• GitHub Login: @mdgattuso
• Microsoft Alias: magattus

[msrini-MSFT]

@zhalu , "cdnverify.contoso.azureedge.net" is added to validate your domain ownership to Azure CDN.

In "Associate the custom domain with your CDN endpoint" section 5th point you can see that you are asked to give the Custom domain as www.contoso.com or cdn.contoso.com.

Hence it is specified as "http://cdn.contoso.com/my-public-container/my-file.jpg"

Let me know if you have any further questions.

[zhalu]

Thanks a lot for the clarifications! I'm still not clear, in previous steps, CNAME is only configured for cdnverify.www.contoso.com, how can it work if we enter URL http://cdn.contoso.com/my-public-container/my-file.jpg in Verify the custom domain step?

[msrini-MSFT]

@zhalu , Got it. Take a look into the statement, "if your custom domain is cdn.contoso.com, the URL to the cached file should be similar to the following URL: http://cdn.contoso.com/my-public-container/my-file.jpg."

If it is cdn.contoso.com then the URL is http://cdn.contoso.com/my-public-container/my-file.jpg. I agree that in the example it is www and here the subdomain is cdn. Will do a PR and change it to www to avoid confusion.

[msrini-MSFT]

PR is done: https://github.com/MicrosoftDocs/azure-docs-pr/pull/81662

Changes will be reflected soon.

[VillainJoKeR]

Adding CNAME entry according to the section "Map the temporary cdnverify subdomain" results in the following problem:

Since only "contoso.azureedge.net" exists and "cdnverify.contoso.azureedge.net" does not, we have no means to verify if our custom domain "cdnverify.www.contoso.com" is working or not by following instructions mentioned in section "Verify the custom domain".

If we add CNAME with "cdnverify.www.contoso.com" and value as "contoso.azureedge.net", adding the custom domain "www.contoso.com" to CDN Profile in Azure Portal as mentioned in "Associate the custom domain with your CDN endpoint" fails since "www.contoso.com" Azure is unable to verify a valid CNAME entry pointing to "contoso.azureedge.net".

I have been stuck at this for 2 days now since any update to either goDaddy or Azure CDN takes hours to get updated. I cannot believe that Microsoft's documentation is this ambiguous. Does anybody not verify what is written in the documentation or have i done something really wrong. I just don't understand!

[stijnherreman]

@msrini-MSFT please take another look at this.

Step 4 is 'Verify the custom domain' and step 5 is 'Map the permanent custom domain'. When at step 4, www.contoso.com is not yet pointing at the CDN endpoint, there is only cdnverify.www.contoso.com

cdnverify.contoso.azureedge.net does not resolve, so it's seemingly impossible to verify that everything is working correctly, before moving on to step 5.