Mapping apex domain to Azure Front Door and afdverify

%3CLINGO-SUB%20id%3D%22lingo-sub-2809073%22%20slang%3D%22en-US%22%3EMapping%20apex%20domain%20to%20Azure%20Front%20Door%20and%20afdverify%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2809073%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20currently%20trying%20to%20use%20the%20Azure%20Front%20Door%20for%20global%20failover%20in%20between%20two%20webapps.%20We%20ran%20into%20the%20issue%20of%20not%20being%20able%20to%20map%20the%20apex%20domain%20to%20the%20Front%20Door.%20We%20are%20not%20using%20Azure%20DNS%20and%20are%20unable%20to%20create%20an%20apex%20record%20as%20our%20zone%20is%20signed.%3C%2FP%3E%3CP%3EDuring%20a%20call%20with%20Microsoft%20support%20they%20suggested%20a%20temporary%20solution%20to%20create%20CNAME%20record%20pointing%26nbsp%3B%3CSPAN%3Eafdverify.yourdomain.com%20to%26nbsp%3Bafdverify.azurewebappdomain.com%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20is%20working%20but%20he%20warned%20that%20this%20is%20a%20temporary%20solution%20and%20the%20public%20IPs%20of%20the%20Azure%20Front%20Door%20are%20subject%20to%20change.%20I'm%20not%20sure%20I%20understand%20what%20afdverify%20does.%20The%20only%20thing%20I%20found%20is%20that%20this%20is%20used%20as%20a%20method%20to%20prove%20that%20we%20own%20the%20domain.%20And%20if%20I%20don't%20have%20an%20A%20record%20that%20points%20to%20an%20IP%20how%20is%20this%20method%20affected%20by%20the%20Azure%20Front%20Door%20IP%20change.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EHas%20anyone%20found%20a%20different%20solution%20for%20mapping%20the%20apex%20domain%20besides%20using%20Azure%2C%20Amazon%20or%20CloudFlare%20DNS%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETIA%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2809073%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Front%20Door%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2809716%22%20slang%3D%22en-US%22%3ERe%3A%20Mapping%20apex%20domain%20to%20Azure%20Front%20Door%20and%20afdverify%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2809716%22%20slang%3D%22en-US%22%3E%3CP%3ECorrection%2C%20the%20CNAME%20entry%20points%20afdverify.yourdomain.com%20to%20afdverify.azurefrontdoordomain.com%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We are currently trying to use the Azure Front Door for global failover in between two webapps. We ran into the issue of not being able to map the apex domain to the Front Door. We are not using Azure DNS and are unable to create an apex record as our zone is signed.

During a call with Microsoft support they suggested a temporary solution to create CNAME record pointing afdverify.yourdomain.com to afdverify.azurewebappdomain.com

 

This is working but he warned that this is a temporary solution and the public IPs of the Azure Front Door are subject to change. I'm not sure I understand what afdverify does. The only thing I found is that this is used as a method to prove that we own the domain. And if I don't have an A record that points to an IP how is this method affected by the Azure Front Door IP change.

Has anyone found a different solution for mapping the apex domain besides using Azure, Amazon or CloudFlare DNS

 

TIA

 

1 Reply

Correction, the CNAME entry points afdverify.yourdomain.com to afdverify.azurefrontdoordomain.com