ASE内部ISE /子域已经消失 [英] ASE Internal ISE / Subdomain has disappeared

问题描述

我一直在用内部ISE创建几个ASE，为生产部署做准备......今天我觉得它的反应不同。 我有一个ASE，但子域是错的。 我删除了ASE，等待了大约20分钟以确保
没有名称冲突并尝试再次创建它。 但是，这一次，当"内部类型"时，子域字段不会显示 选择如下所示...点击"向导"按钮审核显示域为
Azure域，而不是之前尝试的子域 - 是使用Azure DNS的内部域，与外部域相同？ 我没有找到任何文档，当前文档也不是本文档中的屏幕截图：

I've been creating several ASE with an Internal ISE in preparation for a production deployment...and today I feel it's reacting differently.  I had an ASE, but the subdomain was wrong.  I deleted the ASE, waiting some 20 min to ensure that there would be no name conflicts and tried to create it again.  This time however, the subdomain field does not appear when "Internal Type"  is selected see below... clicking through the "wizard" the review shows the domain to be the Azure domain, as opposed to the subdomain as in previous attempts - is the internal domain using Azure DNS in the same way as external???  I have not found any documentation, nor is the current document current withe screen shots in this documentation:

https://docs.microsoft。 com / zh-CN / azure / app-service / environment / create-ilb-ase

推荐答案

采用ILB ASE的阻碍之一是ILB ASE证书。为了简化设置过程和采用，我们正在转向使用DNS后缀< asename> .appservicenvironment.net 创建ILB ASE的地方。针对此ASE制作的应用程序将不会出现在公共DNS中，并且您仍然可以根据需要配置自定义域名。 通过使用我们控制下的域名，您将不再需要担心设置ILB ASE证书。这意味着您只需要为您的个人应用程序提供证书
，而不是整个ILB ASE的通配符证书。

One of the blockers to adopting ILB ASE was the ILB ASE cert. To simplify the setup process and adoption, we are moving to where we create an ILB ASE with the DNS suffix of <asename>.appservicenvironment.net  The apps made against this ASE will not be in the public DNS and you still have the ability to configure custom domain names as you see fit.  By using a domain name under our control, you will no longer have to fret over setting the ILB ASE cert up. This means you only need to provide certs for your individual apps, rather than a wildcard cert for the entire ILB ASE.

如果您更喜欢旧体验，那么您应该能够单击屏幕截图顶部的横幅以返回经典体验。

If you prefer the old experience, you should be able to click the banner on the top of your screenshot to go back to the classic experience.

应立即推出文档更新/博客以突出显示这些更改。

Doc updates/blogs should be rolling out shortly to highlight these changes.

这篇关于ASE内部ISE /子域已经消失的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！