Closed mohijazi closed 2 years ago
@mohijazi I have assigned the issue to the content author for further review.
Hi @mohijazi
Thank you for your patience.
After the domain is verified, delete the DNS TXT record you created. This statement is in # 3 of Step1.
I hope this helps.
Only way around it seems to be using the Powershell as detailed in Tutorial: Create DNS records in a custom domain for a web app: eg
New-AzDnsRecordSet -ZoneName contoso.com -ResourceGroupName "MyAzureResourceGroup" `
-Name "www" -RecordType "CNAME" -Ttl 600 `
-DnsRecords (New-AzDnsRecordConfig -cname "contoso.azurewebsites.net")
[Enter feedback here] At the step "3.1", the Doc was guiding us to create a CNAME DNS record. However, at step 1, we already created TXT record for the same name/FQDN.
If we are trying to put both of the TXT and CNAME record on the Azure DNS, we will be ended up with the following error : Failed to create record set Failed to create record set 'web'. Error: The record could not be created because a CNAME record with the same name already exists in this zone.
This is an expected error per to the RFC : https://docs.microsoft.com/en-us/azure/dns/dns-zones-records#cname-records
The Youtube video didn't use Azure DNS, it was using 3rd party DNS zones, hence, the above error didn't appear.
We know that the TXT record needed for verification, so maybe we can get rid of it once we complete the verification step or I am not sure if the B2C allows us to use other Name/FQDN for the TXT record. In either way, the CX needs to be notified about this error.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.