Custom Domain for Azure Static Web APP Keeps Failing to Validate even with the correct DNS Record CNAME

Question

Custom Domain for Azure Static Web APP Keeps Failing to Validate even with the correct DNS Record CNAME

CB 0

User's image

Any ideas?

Joseph Tran 3,970 Reputation points Independent Advisor

2025-11-06T02:50:35.9933333+00:00
Hi, There

Based on your provided picture, don’t worry that “validation failed” message sometimes pops up a lot. It usually just means Azure can’t see your CNAME record yet, even if you’ve set it right.

So to clarify it more correctly help me to do this first and let me know the result:

Double-check your DNS: make sure your subdomain like www.yourdomain.com or something like that and its points to your Azure app URL something like cool-site.azurestaticapps.net.

If you’re using Cloudflare, turn off the orange cloud for now Azure needs to see the real record, not the proxy.

Give it a bit of time. Sometimes it takes 30–60 minutes for DNS to refresh.

Then try removing the domain in Azure and adding it again. It often works right away after that.
CB 0 Reputation points

2025-11-06T14:48:05.64+00:00
I have confirmed the DNS record

I am using godaddy - there is no proxy

I tested with nslookup command and it return the correct record

Record has been created for over 48 hours now

I have tried removing and re-adding the custom domain Still gets the same error
Shree Hima Bindu Maganti 6,200 Reputation points Microsoft External Staff Moderator

2025-11-10T09:51:07.5166667+00:00

Hi @CB
This issue where the custom domain for Azure Static Web App fails to validate even with the correct CNAME record has been seen frequently. This problem usually happens because Azure cannot detect the CNAME record or because the validation method used is outdated. For newer or Enterprise Grade Edge Static Web Apps, Azure now requires TXT record validation instead of CNAME, which resolves most validation failures.

In cases where users confirmed the DNS record was correct (using GoDaddy or similar registrars), validation still failed due to registrar limitations or conflicting records. If you are using the root domain (yourdomain.com), GoDaddy does not support ALIAS or ANAME records required by Azure, so it’s recommended to map a subdomain like www.yourdomain.com instead. Also, ensure no restrictive CAA records are blocking Microsoft or DigiCert from issuing the certificate

If you’ve already waited more than 48 hours and confirmed the DNS is public, remove and re-add the custom domain using the TXT record method, wait for the validation to complete, and then Azure should issue the certificate automatically.

switching to the TXT validation method, avoiding apex domains with GoDaddy, and verifying CAA record settings have resolved this issue for most users.
https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain?utm_source=chatgpt.com
https://learn.microsoft.com/en-us/answers/questions/1626287/cant-register-static-web-apps-to-a-specific-domain?utm_source=chatgpt.com
https://learn.microsoft.com/en-us/answers/questions/1190071/static-web-app-custom-domain-validation-keeps-fail?utm_source=chatgpt.com
Let me know if you have any further assistances needed.