Custom domain stays in "validating"

Question

Custom domain stays in "validating"

Mario Enrique Mora Chacón 0

I am unable to add my custom domain to my Azure app. I have tried deleting the domain and trying again multiple times, followed the existing solutions, using AI for assistance, but it has been no help. I need someone to give me a hand with this.

The problem is that after I follow the configuration instructions, the domain will remain in "Validating" for a couple of days until it times out and says "An unknown error has occurred while adding your custom domain. Please try again later.".

Really, I am begging you not to send me one more instructions set from Microsoft, because I have been dealing with them for over a week without seeing any kind of positive outcome.

Alekhya Vaddepally 910 Reputation points Microsoft External Staff Moderator

2025-05-09T00:10:25.7366667+00:00
Hi Mario Enrique Mora Chacón,

The "valid" state is usually waiting to confirm the ownership of your custom domain through Azure DNS verification. If this is not confirmed (wrong DNS records, delays in proliferation, or being a mismatched in the host), it remains in the limbo and eventually stays out several times - as you have experienced.

Even if your records look correct, some hidden issues can block verification:DNS proliferation can be delayed (it may take up to 48 hours, but often resolves rapidly).Wrong TXT or CNAME record (a small typo verification may fail quietly).Conflicting records or existing bindings in other azure resources.CDN or DNS-level cashing that causes stale verification data.

Double-check the hostname you are adding (eg, www.yourdomain.com vs yourdomain.com). Azure is strict about matching the accurate subdomain.If it asks for a TXT record (normal for root domain), be sure to add it as shown.If it provides a CNAME, make sure that it is added under the correct subdoman in your DNS manager.

To confirm that the required TXT or CNAME records of Azure are actually visible on the Internet such as https://dnschecker.org/ such as DNS checkers.

If you have just added records, wait for ~ 30 minutes to an hour, and then remove the custom domain from the azure and add it again.If everything else fails, use app service managed certificate as a decline.

Sometimes issues of domain verification are associated with SSL Certs. Consider using the underlying certificate provision of Azure after the domain is valid.
Add a custom domain to Azure App Service
if you have any further concerns or queries, please feel free to reach out to us.
TP 118.8K Reputation points Moderator

2025-05-09T00:26:40.09+00:00

Hi Mario,

Do you have time to work on it now? I can walk you through the process, step-by-step, and I can verify as we go that you created each record properly.

-TP
Alekhya Vaddepally 910 Reputation points Microsoft External Staff Moderator

2025-05-09T17:56:48.6533333+00:00

Hi Mario Enrique Mora Chacón,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mario Enrique Mora Chacón 0 Reputation points

2025-05-09T21:27:26.7533333+00:00

Hello TP, I would be glad if we could set up some time whenever it is convenient for you. I'm in Madrid (UTC +02:00).

Your answer

Alekhya Vaddepally 910 Reputation points Microsoft External Staff Moderator

2025-05-09T00:10:25.7366667+00:00

Hi Mario Enrique Mora Chacón,

The "valid" state is usually waiting to confirm the ownership of your custom domain through Azure DNS verification. If this is not confirmed (wrong DNS records, delays in proliferation, or being a mismatched in the host), it remains in the limbo and eventually stays out several times - as you have experienced.

Even if your records look correct, some hidden issues can block verification:DNS proliferation can be delayed (it may take up to 48 hours, but often resolves rapidly).Wrong TXT or CNAME record (a small typo verification may fail quietly).Conflicting records or existing bindings in other azure resources.CDN or DNS-level cashing that causes stale verification data.

Double-check the hostname you are adding (eg, www.yourdomain.com vs yourdomain.com). Azure is strict about matching the accurate subdomain.If it asks for a TXT record (normal for root domain), be sure to add it as shown.If it provides a CNAME, make sure that it is added under the correct subdoman in your DNS manager.

To confirm that the required TXT or CNAME records of Azure are actually visible on the Internet such as https://dnschecker.org/ such as DNS checkers.

If you have just added records, wait for ~ 30 minutes to an hour, and then remove the custom domain from the azure and add it again.If everything else fails, use app service managed certificate as a decline.

Sometimes issues of domain verification are associated with SSL Certs. Consider using the underlying certificate provision of Azure after the domain is valid.
Add a custom domain to Azure App Service
if you have any further concerns or queries, please feel free to reach out to us.
TP 118.8K Reputation points Moderator

2025-05-09T00:26:40.09+00:00

Hi Mario,

Do you have time to work on it now? I can walk you through the process, step-by-step, and I can verify as we go that you created each record properly.

-TP
Alekhya Vaddepally 910 Reputation points Microsoft External Staff Moderator

2025-05-09T17:56:48.6533333+00:00

Hi Mario Enrique Mora Chacón,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mario Enrique Mora Chacón 0 Reputation points

2025-05-09T21:27:26.7533333+00:00

Hello TP, I would be glad if we could set up some time whenever it is convenient for you. I'm in Madrid (UTC +02:00).

Share via

Custom domain stays in "validating"

Your answer