GO BACK, DO NOT SECURE

Yesterday at around 3 p.m., I set up awverifying records for two websites that I want to transfer from one Azure account to another. By the end of the day, Azure still did not allow me to add my domains, so I took a gamble and re-pointed the domain and www subdomain to the new IP address. This morning, of course, my sites were down, and Azure still does not accept my domains. I had to specify the domain and www subdomain back to the old IP.

Obviously, I expect an answer that the CNAME error did not propagate, but my DNS and others that I checked online changed within an hour. Why does Azure take 18 hours and count?

I'm sure I set it right ... Azure error requesting AWVERIFY CNAME

DNS lookup for AWVERIFY showing the correct CNAME

DNS control panel

+1
1

, . , Azure . , Azure - ( ) .

, .

, , -, , .

+1

Source: https://habr.com/ru/post/1536681/


All Articles