AWVERIFY不适用 [英] AWVERIFY not propergating

问题描述

昨天下午3点左右，我设置了两个网站的awverify记录，我想从一个Azure帐户转移到另一个。到最后，Azure仍然不允许我添加我的域名，所以我冒着赌注，并将域和www子域重新指向新的IP。今天早上我的网站当然不好，Azure仍然不接受我的域名。我不得不将域名和www子域名指向旧的IP。

Yesterday at about 3pm, I setup awverify records for two website I want to transfer from one Azure account to another. By the end of the day Azure still wasn't allowing me to add my domains, so I took a gamble and re-pointed the domain and www sub-domain to the new IP. This morning of course my sites were down and Azure still won't accept my domains. I've had to point the domain and www sub-domain back to the old IP.

显然，我期待着这个错误CNAME没有传播的响应，但是我的DNS和我在线检查的其他人在一小时内就改变了。为什么Azure需要18个小时计算？

Obviously I'm expecting the response that the awverify CNAME hasn't propagated, but my DNS, and others I checked online, changed within an hour. Why would Azure take 18 hours and counting?

我确定我已经正确设置了...

I'm quite sure I've set it up correctly...

推荐答案

我找到答案，虽然我可以在其他地方找不到。问题的原因是我正在从一个Azure帐户迁移到另一个。似乎Azure不会允许两个网站（即使在不同的帐户）使用相同的主机名。

I found the answer, though I can't find this documented elsewhere. The cause of the issue is that I was migrating from one Azure account to another. It seems that Azure will not allow two website (even in different accounts) to use the same host names.

一旦我从旧帐户中删除了主机名，我就是能够将它们添加到新帐户。

Once I deleted the host names from the old account, I was able to add them to the new account.

我可以看到为什么会是这种情况，但是应该记录在某个地方，因为我不能成为第一个能够运行的人。

I can see why this would be the case, but it should be documented somewhere as I can't be the first person to run in to this.

这篇关于AWVERIFY不适用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！