Domain ownership not working - azure dns resolvers failing

Simple User 1 Reputation point
2021-03-29T03:02:59.227+00:00

I had a subdomain pointing to an azurewebsite that was working properly. The Subdomain was pointing via cname to the azurewebsite resource and it was working. I deleted the resource and then created the same exact resource in another account. The DNS records are correct as when I browse to my subdomain I get the usual "404 Web Site not found" from azure. I am trying to add the same exact custom domain that was working before and now it isn't. I am looking at the records with "dig @1.1.1.1 subdomain" and I am seeing perfectly the cname azure tells me to add, it is there but something isn't working. I don't know if azure DNS resolvers are failing or it is something else (dns resolvers from google and cloudfront shows the cname is there) but I can't add the custom domain even thought the cname is there and the DNS records are perfectly fine. This is happening with multiple azurewebsite resources I am migrating to another azure account. I didn't touch the records so they should be working perfectly and they aren't

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,963 questions
{count} votes