Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are trying to validate the custom domain in AFD.
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!
Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution and provide my comments as well.
Issue:
- The UI in Configure a custom domain on Azure Front Door is misleading
Analysis:
- I am afraid the documentation is actually using AFD's UI and not Azure DNS's UI.
- i.e.,
- The UI is not of the DNS Zone in Azure, instead of the AFD's FQDN value to be updated in the DNS Zone
- If you were to see the DNS Zone in Azure, the record name would be "_dnsauth.contoso" only
- The record here actually is "_dnsauth.contoso"
- The UI from AFD shows "_dnsauth.contoso.fabrikam.com" as the complete FQDN (to let the customers know which DNS Zone is being used here)
- Since this is using Azure DNS example, this will automatically update the DNS Zone "fabrikam.com" with the record "_dnsauth.contoso" and the effective FQDN becomes "_dnsauth.contoso.fabrikam.com" as shown in UI
- Per your original configuration, your FQDN was "_dnsauth.contoso.fabrikam.com**.fabrikam.com**"
- Which is obviously incorrect.
- Per your new configuration, the FQDN becomes "_dnsauth.contoso.fabrikam.com"
- Which is the correct one.
- TL:DR ;
- "_dnsauth.contoso.fabrikam.com" is not the record name, it's the entire FQDN.
- "_dnsauth.contoso" is the record name.
Please let us know if we can be of any further assistance here.
Thanks,
Kapil
Please Accept an answer if correct.
Original posters help the community find answers faster by identifying the correct answer.