Custom domain https://searchinger.com/ not validating for Azure App Service despite correct CNAME setup

Question

I’m trying to map [searchinger.com] to an Azure App Service, and the domain validation keeps failing even though the CNAME record is already in place and resolves correctly from external DNS tools.

I’ve set the CNAME to point to the app’s [azurewebsites.net] hostname, and DNS propagation looks complete. Azure still shows “Ownership not verified.”

Is there anything specific Azure checks beyond the standard CNAME lookup? Trying to understand whether this is a caching delay or if there’s another requirement I’m missing.

Answer 1

Hi @Jane wang
Even if the CNAME record resolves properly with external DNS tools, Azure App Service requires more than just DNS resolution to verify ownership. You also need to add a TXT record in the format asuid.<yourdomain> with the verification ID shown in the Custom Domains section. Without this TXT record, the portal will still display “Ownership not verified,” even if the CNAME is set up correctly.

If you’re setting up a root (apex) domain like searchinger.com, remember that DNS standards don’t allow CNAME records at the root. In this situation, you should use an A record pointing to the App Service IP address and include the required TXT verification record.

Also, make sure the domain isn’t behind a proxy (such as Cloudflare proxy mode), since Azure needs to resolve the DNS record directly for validation.

If DNS propagation is complete and the TXT record is correct, you can also try removing and re-adding the custom domain in the App Service blade to refresh the validation process.

https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain
https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-custom-domain-issues-azure-app-service
Let me know if you have any further assistances needed.