This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 59%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF8%3C/text%3E%3C/svg%3E)
Trying to delete a custom domain on a CDN but get the following error. This was a PoC for a bug bounty but can't seem to delete my custom domain on the CDN resource. How would I go about actually deleting it? (Without updating the DNS)
I already tried:
az feature register --namespace Microsoft.Network --name BypassCnameCheckForCustomDomainDeletion
but to no avail.
The error message is:
(Conflict) Cannot delete custom domain "XXXX" because it is still directly or indirectly (using "cdnverify" prefix) CNAMEd to CDN endpoint "XXXX.azureedge.net".
Please remove the DNS CNAME record and try again.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 28.000000000000004%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETK%3C/text%3E%3C/svg%3E)
I have identical issue.
Also run
az feature register --namespace Microsoft.Network --name BypassCnameCheckForCustomDomainDeletion
waited till
az feature list -o table --query "[?contains(name, 'Microsoft.Network/BypassCnameCheckForCustomDomainDeletion')].{Name:name,State:properties.state}"
shows that the feature got registered,
still unable to delete the endpoint
Did anyone figure out why this happens?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 91%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EW%3C/text%3E%3C/svg%3E)
It's absurd the way Microsoft behaves with DNS entries. They are completely out of touch with how DNS work is performed in the real work. There are plenty of scenarios where one organization is in control of DNS and another separate organization is in control of the cloud environment. Requiring DNS changes before making changes prevents a lot of prework and sometimes makes using certain services impossible because some organizations I work with have an issue with creating these fake "verify" records. They just flat out won't do it. AWS doesn't do anything like this, because they are intelligent enough to know that if you don't control DNS (the REAL DNS server) you can't do anything harmful to the masses if you setup a service on a DNS name you do not own. Sure you can prevent the real owners of the DNS name from using it, but that's an easy solve. Let the owners have an override method to prove ownership. If I can create a CNAME record with an Azure endpoint I own, that should be all that is required to prove I own it and allow me to override. It's this backwards thinking that has me closing my Azure account and moving to AWS and not looking back. While the interface takes some getting used to by comparison, the AWS service is lightyears ahead of Azure.
az feature register --namespace Microsoft.Network --name BypassCnameCheckForCustomDomainDeletion is not the correct fix for a CDN custom domain. The correct fix is az feature register --namespace Microsoft.Cdn --name BypassCnameCheckForCustomDomainDeletion.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 78%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
Yet another reason to add to the myriad of ways that Azure will steal your time in an unbelievably frustrating way!
Also, it didn't even work. Had to delete the DNS entries, which makes NO sense. There should be an override!