简体   繁体   English

分配给通过 Azure 门户部署的容器组的 FQDN 的随机部分是多少?

[英]What is the random portion of the FQDN assigned to a container group deployed through the Azure portal?

When I deploy an instance through the portal, the structure of the FQDN my container is assigned is:当我通过门户部署实例时,我的容器分配的 FQDN 的结构是:

{domain label}.{seemingly random string}.{region}.azurecontainer.io

Deleting & redeploying an identical instance yields the same random string portion, so at least it's not randomized for each deployment, but as this does not conform to the structure defined here in the Azure docs , I'm left without any explanation.删除和重新部署相同的实例会产生相同的随机字符串部分,因此至少它不是每次部署都随机的,但由于这不符合Azure 文档中定义的结构,我没有任何解释。 Is it a hash?是 hash 吗? An id?身份证? How can this be predicted before deployment?如何在部署前预测到这一点?

I believe this is related to Prevent dangling DNS entries and avoid subdomain takeover and ACI DNS name reuse policy :我相信这与Prevent dangling DNS entries and avoid subdomain takeoverACI DNS name reuse policy 有关

In order to avoid this, ACI will now allow customers to reuse DNS names while preventing DNS names from being reused by different customers.为了避免这种情况,ACI 现在将允许客户重复使用 DNS 名称,同时防止 DNS 名称被不同的客户重复使用。 ACI secures DNS names by randomly generating a hash value to associate with the DNS name, making it difficult for another customer to accidentally create an ACI with the same name and get linked to the past customer's ACI information. ACI 通过随机生成与 DNS 名称相关联的 hash 值来保护 DNS 名称,从而使其他客户很难意外创建具有相同名称的 ACI 并链接到过去客户的 ACI 信息。

There are five "reuse levels" that use hashing to generate a unique DNS name for your container group:有五个“重用级别”使用哈希为您的容器组生成唯一的 DNS 名称:

  • noReuse - no hash, object's DNS name cannot be reused. noReuse - 没有 hash,对象的 DNS 名称不能被重复使用。
  • unsecure - hash is based on the DNS name only (aka Any Reuse). unsecure - hash 仅基于 DNS 名称(又名 Any Reuse)。
  • tenantReuse (default) - hash is based on the DNS name and Tenant ID. tenantReuse (默认) - hash 基于 DNS 名称和租户 ID。
  • subscriptionReuse - hash is based on the DNS name, the tenant ID and subscription ID. subscriptionReuse - hash 基于 DNS 名称、租户 ID 和订阅 ID。
  • resourceGroupReuse - hash is based on the DNS name, the tenant ID, subscription ID and resource group name. resourceGroupReuse - hash 基于 DNS 名称、租户 ID、订阅 ID 和资源组名称。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 如何在 portal.azure.com 中按类型默认概览仪表板 - How to default overview dashboard as group by type in portal.azure.com Azure 容器实例 FQDN - 我如何在 ARM 中设置它(使用 az create 不起作用) - Azure Container Instance FQDN - how do I set it in the ARM (using az create does not work) Azure容器组的多个出口IP - Multiple egress IPs for Azure Container Group 什么是 Azure 私有 DNS 区域组? - What is Azure Private DNS Zone Group? 通过公共 IP 地址获取 Azure FQDN(DNS 名称) - Get Azure FQDN (DNS Name) by Public IP Address 通过 Azure 门户配置将 Key Vault 证书的指纹发送到服务总线主题 - Sending Thumbprint of a Key Vault Certificate to Service Bus topic through Azure Portal configuration 使用系统从 VM 分配的托管标识连接到 azure 容器注册表时出错 - Error connecting to azure container registry using system assigned managed identity from a VM 在 GCP 中,azure 可用性集、azure 磁盘外部、azure.network 接口、azure 资源组的替代方案是什么 - what is an alternative of azure availability set, azure disk external, azure network interface, azure resource group, in GCP Azure .net:在没有 Azure 防火墙的情况下控制到 fqdn 的流量 - Azure Vnet: Control traffic to fqdn without Azure Firewall 如何使用python在azure .net中创建新的容器组 - How to create new container group in azure vnet using python
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM