Azure Front Door Instance DNS State "CNAME/alias record is not currently detected"

hampton123 1,160 Reputation points

I've been following this MS tutorial to connect my Front Door instance to a custom domain. My endgoal is to connect my Azure Front Door instance to my static website and give the static website the custom domain. I've completed the steps up to "Switch between certificate types". In my Azure Front Door instance, my domain is input with the certificate, however the DNS state is "CNAME/alias record is not currently detected". Everything else is fine though, the validation state is "Approved", the provisioning state is "Succeeded", and the certificate state is deployed. However, how would I adjust this issue with the DNS state?

Azure Front Door
Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
627 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,625 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ChaitanyaNaykodi-MSFT 24,666 Reputation points Microsoft Employee


    Thank you for reaching out.

    Can you please confirm if you have added the custom domain on the Azure Front Door aswell?

    If yes, as documented here

    When you add a domain to your Azure Front Door profile, you configure two records in your DNS server:

    • A DNS TXT record, which is required to validate ownership of your domain name. For more information on the DNS TXT records, see Domain validation.
    • A DNS CNAME record, which controls the flow of internet traffic to Azure Front Door.

    Can you please confirm if you have added CNAME record?

    Meanwhile as documented here

    If your domain CNAME is indirectly pointed to an Azure Front Door endpoint, for example, by using Azure Traffic Manager for multi-CDN failover, the DNS state column shows as CNAME/Alias record currently not detected. Azure Front Door can't guarantee 100% detection of the CNAME record in this case. If you configured an Azure Front Door endpoint to Traffic Manager and still see this message, it doesn't mean that you didn't set up correctly. No further action is necessary from your side.

    Thank you!

    0 comments No comments