[BUG] After successfully creating a custom domain name for API Management, it deletes itself

Morris Kurz 20 Reputation points

Hello everyone,

I want to create a custom domain name for my Consumption tier API Management instance. After adding the hostname for type Gateway with a managed certificate, I setup my DNS record (CNAME) to point to the APIM URL and a TXT record to verify my ownership of the domain. After saving everything in the API Management instance, I get the notification that the hostnames were updates successfully. But the newly added domain removes itself in the portal after a few seconds, ending in the initial state of the default APIM URL. I validated that the URL does not work by doing a POST request, ending in a 404 error. This persists even after three days of waiting, in case the configuration takes some time to load to every server.

TL;DR The portal notified me of the successful creation of the hostname, but the hostname wasn't created and can't be used.User's image

User's image

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
1,930 questions
{count} votes

Accepted answer
  1. MuthuKumaranMurugaachari-MSFT 22,266 Reputation points

    Morris Kurz Sure, you are welcome. Glad it got resolved. Microsoft Q&A has policy: Accept an answer that question authors cannot accept their own answers and hence I am posting your answer in case you like to accept so that it can benefit others facing similar issues.


    We found that adding managed certificate failed with an error due to presence of a CAA record that does not authorize Digicert. Morris Kurz followed the steps described in DNS configuration and created a CAA domain record with the value: 0 issue digicert.com to resolve the issue.

    User's image

    I hope this helps.


    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more