CDN Domain name stopped resolving (<cdn>.azureedge.net) and now I can't delete

James Kiefer 1

My CDN has been untouched for literal months and today the DNS just completely stopped working. I have another CDN configured exactly the same way and it is working.

I started trying to delete it and it was complaining about CNAME's so I had to strip all the configuration out of my domain and now I'm looking at completely bare zones. It's still not allowing me to delete the CDN (claiming a CNAME exists) so that I can recreate it and get my website back up.

I don't really know where to go since I can't create a ticket and I can't delete the resource...

KapilAnanth-MSFT 34,766 Reputation points Microsoft Employee

2022-11-17T06:07:28.24+00:00

Hi @James Kiefer ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are facing issues with deleting your CDN.

Can you please open a dig interface and check if your CNAME(FQDN) is still resolving to CDN's/Azure endPoint?

Thanks,
Kapil
James Kiefer 1 Reputation point

2022-11-17T14:34:28.823+00:00

Looking at my DNS nameserver configuration and checking with local dig and the tool you just sent shows nothing pointed to the CDN. I had to add some configuration back in an attempt to get my website back by pointing the domain directly at the static web app instead of the CDN. Now my SSL is broken and I have no CDN.

I'm still getting the exact same error when trying to delete the resource. Enabling BypassCnameCheckForCustomDomainDeletion does nothing.

BTW, what is the uptime guarantee of CDNs? My website was not running on the CDN due to DNS issues on Azure's end for nearly 24 hours and now I'm still down due to a bug in your portal not allowing me to recreate my resources.
James Kiefer 1 Reputation point

2022-11-17T14:52:21.253+00:00

I definitely tried this multiple times last night but deleting the entire CDN instead of the endpoint has finally worked.
James Kiefer 1 Reputation point

2022-11-17T14:58:57.057+00:00

I've recreated my CDN now and I still have the same problem of the <cdn>.azureedge.net DNS name not resolving to an IP. I have another CDN setup the exact same way and it does resolve to an IP. When I dig on the domains, the working one has an additional CNAME record that the broken one does not.
James Kiefer 1 Reputation point

2022-11-17T20:34:23.527+00:00

I've changed the terraform to append a -b onto the end of my resource name and that one comes up with DNS that works. So to recap, my managed DNS of the CDN comes up broken regardless of region if I use the old name and works if I use a new one. :'(
KapilAnanth-MSFT 34,766 Reputation points Microsoft Employee

2022-11-18T04:27:52.657+00:00

Hi @James Kiefer ,

I see you have done a ton of troubleshooting and made good progress.

At this point, I believe to troubleshoot the exact issue, I think we will need a specialized 1:1 session, where a support engineer can have a screen share session to pinpoint the issue.
If you have a support plan you may file a support ticket, else please do let us know, we will try and help you get a one-time free technical support.

Cheers,
Kapil
James Kiefer 1 Reputation point

2022-11-22T15:40:51.223+00:00

I have moved my website over to github pages which turns out is a lot easier to use on-top of being free.

I've left the CDN configured and although I've been busy I have kept an eye on it and it is still broken.