Unable to create a custom domain in Azure Front Door because a "custom domain with the same host name already exists"

Question

I am creating a Front Door standard tier route and adding a set of domain names. All but one have been added successfully.

A attempt to add a specific domain name (in fact a www subdomain) fails repeatedly with the error: Failed to create the custom domain 'www-foo-org-uk-xxxx'. Error: We couldn't create your custom domain. Another custom domain with the same host name already exists.

However, no such duplicate domain name exists in the list displayed in the portal. So I am unable to add the name, and if the name exists already I can't see it so I can't add it to the route/endpoint.

This looks like a bug in the azure portal. How do I resolve this?

Answer 1

Hello James Munro,

Thanks for your question.

Based on prior issues similar to this you may need to create a support Request.

See similar solution here: https://learn.microsoft.com/en-us/answers/questions/1036592/azure-frontdoor-standard-not-able-to-reuse-a-previ

https://azure.microsoft.com/en-us/support/create-ticket

You can mark it 'Accept Answer' and 'Upvote' if this helped you

Regards,

Abiola

Answer 2

Hi @James Munro,

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution.

Please click "Accept" the answer as original posters help the community find answers faster by identifying the correct answer.

Issue:

Unable to create a custom domain in Azure Front Door because a "custom domain with the same host name already exists"

 

Resolution:

It turned out that the domain was being used in my subscription, but in a different (legacy) CDN resource. So it seems that a domain can only be used one in the subscription (or perhaps even in a wider scope?).

Once I removed the domain from the legacy CDN, I was able to use it within the Front Door resource.

---

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.