Azure 外部端点配置
我正在尝试将两个外部终结点添加到 Azure 流量管理器。
我在 Firebase 托管和 GCP App Engine（两个区域）中托管了两个 React 应用程序（同一应用程序），
https://XXXXX-alt.el.r.appspot.com/sign-in
https://XXXXXX.web.app/sign-in
我添加了“cardynnasty-alt.el.r.appspot.com”和“cardynnastyadmin.web.app”作为端点我遇到了两个问题。
一是流量管理器 URL 是 http，这会发出警告。二是找不到资源。
我对这个主题很陌生，想知道如何配置自定义域来解决这个问题。我怀疑第一步是从 namecheap 或 godaddy 或其他地方购买 2 个域名。
我不确定接下来的步骤。我购买了 namecheap 域名并添加了 DNS，以便现在可以通过 namecheap 域名访问它们。
如何让这些域与 Azure 流量管理器配合使用？只是将它们添加为外部端点会给我带来“路径未找到”错误。
I'm trying to add two External Endpoints to Azure Traffic Manager.
I have hosted two react apps (Same app) in both Firebase Hosting and GCP App Engine (two regions) The URLs are
https://XXXXX-alt.el.r.appspot.com/sign-in
https://XXXXXX.web.app/sign-in
I added "cardynnasty-alt.el.r.appspot.com" and "cardynastyadmin.web.app" as endpoints and I come across 2 issues.
One is, traffic manager URL is http, and this gives a warning. Second is, the resource cannot be found.
I'm quite new to this subject and would like to know how I can configure a custom domain to sort out this issue. I suspect the first step is purchasing 2 domains from namecheap or godaddy or somewhere..
I'm not sure about the next steps.. I purchased namecheap domains and added DNS such that they are now reachable with namecheap domains.
How do I get these domains working with Azure Traffic Manager? Just adding them as external endpoints brings me to "path not found" errors..
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
• 流量管理器URL 为http，因此会发出警告，因为流量管理器在DNS 级别 工作，即应用层（第7 层）。流量管理器使用 DNS 根据流量路由方法的规则将客户端定向到特定服务端点。客户端直接连接到选定的端点。流量管理器不是代理或网关。流量管理器看不到客户端和服务之间传递的流量。
因此，流量管理器 URL 将仍然是 HTTP URL，除非您为要用来代替流量管理器 URL 的自定义域创建 CNAME 记录，即，如果您打算使用 >'apps.cardynasty.com' 作为流量管理器 URL，而不是 'contoso.trafficmanager.net'，那么您需要为以下内容创建 'CNAME' 记录：每当流量管理器被调用时，“contoso.trafficmanager.net”都会重定向到“apps.cardynasty.com”。为此，您需要在公共 DNS 服务器上拥有“cardynasty.com”域，以便处理所述自定义域的各种类型的 DNS 记录。因此，完成后，随着流量管理器 URL 重定向到自定义子域注册 URL，HTTP 错误也将消失。
• 对于第二个问题，您想要为两个完全独立的应用程序配置自定义域，但希望它们的流量由Azure 流量管理器通过单个FQDN 进行管理。为此，由于您已购买这两个应用程序的根域，即'appspot.com'和'web.app' ，您拥有为这两个域创建和处理各种类型的 DNS 记录的唯一所有权。因此，现在您必须为使用根域作为 DNS 主机的应用创建“A”主机记录，即为“cardynnasty-alt.el”创建“A”主机记录在您购买了“appspot.com”域名的公共 DNS 中创建“.r.appspot.com”，并类似地在您购买了“appspot.com”域名的公共 DNS 中为“cardynastyadmin.web.app”创建一条“A”主机记录“web.app”域名。
这样，现在当您在流量管理器中添加指定的“cardynnasty-alt.el.r.appspot.com”和“cardynnastyadmin.web.app”作为外部端点时，重定向将会成功，并且当根据为流量管理器配置文件定义的路由规则搜索“apps.cardynasty.com”页面时，应用程序页面将被正确加载。有关上述内容的更多信息，请参阅下面的文档链接以获取更多参考： -
https://learn.microsoft.com/en-us/azure/traffic-manager/traffic-manager-how-it-works
https://learn.microsoft.com/en-us/天蓝色/流量管理器/流量管理器常见问题解答
• The traffic manager URL is http and thus it gives out a warning because traffic manager works at the DNS level which is at the application layer (Layer 7). Traffic Manager uses DNS to direct clients to specific service endpoints based on the rules of the traffic-routing method. Clients connect to the selected endpoint directly. Traffic Manager is not a proxy or a gateway. The Traffic Manager does not see the traffic passing between the client and the service.
Thus, the traffic manager URL will remain an HTTP URL unless you create a CNAME record for the custom domain that you want to use in place of the traffic manger URL, i.e., if you intend to use ‘apps.cardynasty.com’ as the traffic manager URL instead of ‘contoso.trafficmanager.net’, then you need to create a ‘CNAME’ record for ‘contoso.trafficmanager.net’ to redirect to ‘apps.cardynasty.com’ for the traffic manager whenever it is called upon. And for this purpose, you will need to own the ‘cardynasty.com’ domain on a public DNS server for handling various types of DNS records for the said custom domain. Hence, when done, the HTTP error will also vanish as the traffic manager URL is redirected to a custom subdomain registered URL.
• And for the second issue that you want to configure custom domain for your two altogether separate apps but want their traffic to be managed by an Azure traffic manager through a single FQDN. For that purpose, since you have purchased the root domains of both the apps, i.e., ‘appspot.com’ and ‘web.app’, you have the sole ownership of creating and handling various types of DNS records for these two domains. Thus, now you will have to create ‘A’ host records for the apps that are using the root domains as their DNS host, i.e., create an ‘A’ host record for ‘cardynnasty-alt.el.r.appspot.com’ in the public DNS where you have purchased the ‘appspot.com’ domain name and similarly create an ‘A’ host record for ‘cardynastyadmin.web.app’ in the public DNS where you have purchased the ‘web.app’ domain name.
In this way, now when you add the stated ‘cardynnasty-alt.el.r.appspot.com’ and ‘cardynastyadmin.web.app’ as external endpoints in the traffic manager, the redirection will be successful, and the app page will be appropriately loaded up when the ‘apps.cardynasty.com’ page will be searched for according to the routing rules defined for the traffic manager profile. For more information regarding the above, kindly refer to the documentation link below for more reference: -
https://learn.microsoft.com/en-us/azure/traffic-manager/traffic-manager-how-it-works
https://learn.microsoft.com/en-us/azure/traffic-manager/traffic-manager-faqs