流量管理器路由方法Traffic Manager routing methods

Azure 流量管理器支持使用六种流量路由方法来确定如何将网络流量路由到不同的服务终结点。Azure Traffic Manager supports six traffic-routing methods to determine how to route network traffic to the various service endpoints. 对于任何配置文件,流量管理器将关联到它的流量路由方法应用于它收到的每个 DNS 查询。For any profile, Traffic Manager applies the traffic-routing method associated to it to each DNS query it receives. 流量路由方法确定要在 DNS 响应中返回哪个终结点。The traffic-routing method determines which endpoint is returned in the DNS response.

流量管理器中提供了以下流量路由方法:The following traffic routing methods are available in Traffic Manager:

  • 优先级:如果希望为所有流量提供主服务终结点,请选择“优先级”路由 。Priority: Select Priority routing when you want to have a primary service endpoint for all traffic. 可提供多个备用终结点,以防主终结点或备份终结点之一不可用。You can provide multiple backup endpoints in case the primary or one of the backup endpoints is unavailable.
  • 加权:如果希望基于终结点的权重将流量分配给一组终结点,请选择“加权”路由 。Weighted: Select Weighted routing when you want to distribute traffic across a set of endpoints based on their weight. 请将权重设置为相同,以均匀分布于所有终结点。Set the weight the same to distribute evenly across all endpoints.
  • 性能:如果终结点位于不同的地理位置,并且你希望最终用户依据最低网络延迟使用“最近的”终结点,可以选择“性能”路由 。Performance: Select Performance routing when you have endpoints in different geographic locations and you want end users to use the "closest" endpoint for the lowest network latency.
  • 地理:选择“地理”路由,基于用户的 DNS 查询源自的地理位置,将用户定向到特定终结点(Azure、外部或嵌套) 。Geographic: Select Geographic routing to direct users to specific endpoints (Azure, External, or Nested) based on where their DNS queries originate from geographically. 使用此路由方法,可确保遵守数据主权授权、内容本地化和用户体验以及测量来自不同区域的流量等情况。With this routing method, it enables you to be in compliance with scenarios such as data sovereignty mandates, localization of content & user experience and measuring traffic from different regions.
  • 多值 对于只能包含 IPv4/IPv6 地址作为终结点的流量管理器配置文件,请选择“多值”。 Multivalue: Select MultiValue for Traffic Manager profiles that can only have IPv4/IPv6 addresses as endpoints. 当收到针对此配置文件的查询时,将返回所有正常运行的终结点。When a query is received for this profile, all healthy endpoints are returned.
  • 子网:若要将最终用户 IP 地址范围集映射到特定终结点,请选择“子集”流量路由方法 。Subnet: Select Subnet traffic-routing method to map sets of end-user IP address ranges to a specific endpoint. 当收到请求时,将返回为该请求的源 IP 地址映射的终结点。When a request is received, the endpoint returned will be the one mapped for that request's source IP address.

所有流量管理器配置文件都具有运行状况监视和终结点的自动故障转移。All Traffic Manager profiles have health monitoring and automatic failover of endpoints. 有关详细信息,请参阅流量管理器终结点监视For more information, see Traffic Manager Endpoint Monitoring. 在流量管理器配置文件中,一次只能配置一种流量路由方法。Within a Traffic Manager profile, you can only configure one traffic routing method at a time. 可以随时为配置文件选择其他流量路由方法。You can select a different traffic routing method for your profile at any time. 更改将在一分钟内应用,不会造成任何停机时间。Your changes will be applied within a minute without any downtime. 可使用嵌套的流量管理器配置文件来组合使用多种流量路由方法。You can combine traffic routing methods by using nested Traffic Manager profiles. 使用嵌套配置文件,可以启用复杂的流量路由配置,以满足更大更复杂的应用程序需求。Nesting profiles allows for sophisticated traffic-routing configurations that meet the needs of larger and complex applications. 有关详细信息,请参阅嵌套式流量管理器配置文件For more information, see nested Traffic Manager profiles.

优先级流量路由方法Priority traffic-routing method

组织通常希望为服务提供可靠性。Often an organization wants to provide reliability for their services. 为此,他们部署一个或多个备份服务,以防其主服务出故障。To do so, they deploy one or more backup services in case their primary goes down. Azure 客户可以通过“优先级”流量路由方法来轻松实现此故障转移模式。The 'Priority' traffic-routing method allows Azure customers to easily implement this failover pattern.

Azure 流量管理器的“优先级”流量路由方法

流量管理器配置文件包含服务终结点的优先顺序列表。The Traffic Manager profile contains a prioritized list of service endpoints. 默认情况下,流量管理器将所有流量发送到主终结点(优先级最高)。By default, Traffic Manager sends all traffic to the primary (highest-priority) endpoint. 如果主终结点不可用,流量管理器会将流量路由到第二个终结点。If the primary endpoint isn't available, Traffic Manager routes the traffic to the second endpoint. 如果主终结点和辅助终结点都不可用,流量会转到第三个终结点,依此类推。In a situation where the primary and secondary endpoints aren't available, the traffic goes to the third, and so on. 终结点的可用性取决于配置的状态(已启用或已禁用)和正在进行的终结点监视。Availability of the endpoint is based on the configured status (enabled or disabled) and the ongoing endpoint monitoring.

配置终结点Configuring endpoints

在 Azure 资源管理器中,可以使用每个终结点的“priority”属性显式配置终结点优先级。With Azure Resource Manager, you configure the endpoint priority explicitly using the 'priority' property for each endpoint. 此属性是一个介于 1 和 1000 之间的值。This property is a value between 1 and 1000. 值越小,表示优先级越高。A lower value represents a higher priority. 终结点不能共享优先级值。Endpoints can't share priority values. 该属性的设置是可选的。Setting the property is optional. 如果省略该属性,会根据终结点顺序使用默认优先级。When omitted, a default priority based on the endpoint order is used.

加权流量路由方法Weighted traffic-routing method

使用“加权”流量路由方法可以均匀分布流量,或使用预定义的权重。The 'Weighted' traffic-routing method allows you to distribute traffic evenly or to use a pre-defined weighting.

Azure 流量管理器的“加权”流量路由方法

在“加权”流量路由方法中,需要为流量管理器配置文件中的每个终结点分配一个权重。In the Weighted traffic-routing method, you assign a weight to each endpoint in the Traffic Manager profile configuration. 该权重是从 1 到 1000 的整数。The weight is an integer from 1 to 1000. 此参数是可选的。This parameter is optional. 如果省略此参数,流量管理器将使用默认权重“1”。If omitted, Traffic Managers uses a default weight of '1'. 权重越高,优先级就越高。The higher weight, the higher the priority.

对于收到的每个 DNS 查询,流量管理器会随机选择一个可用终结点。For each DNS query received, Traffic Manager randomly chooses an available endpoint. 选择哪个终结点取决于分配到所有可用终结点的权重。The probability of choosing an endpoint is based on the weights assigned to all available endpoints. 对所有终结点使用相同的权重会导致均匀分布流量。Using the same weight across all endpoints results in an even traffic distribution. 对特定的终结点使用较高或较低的权重会导致这些终结点在 DNS 响应中的返回次数较多或较少。Using higher or lower weights on specific endpoints causes those endpoints to be returned more or less frequently in the DNS responses.

加权方法可以实现一些有用的方案:The weighted method enables some useful scenarios:

  • 应用程序逐步升级:给定要路由到新终结点的流量百分比,并随着时间的推移逐渐将流量增加到 100%。Gradual application upgrade: Given a percentage of traffic to route to a new endpoint, and gradually increase the traffic over time to 100%.
  • 将应用程序迁移到 Azure:创建包含 Azure 终结点和外部终结点的配置文件。Application migration to Azure: Create a profile with both Azure and external endpoints. 调整终结点的权重,优先选择新终结点。Adjust the weight of the endpoints to prefer the new endpoints.
  • 适用于更多容量的云突发:通过将本地部署放在流量管理器配置文件之后,快速将本地部署扩展到云中。Cloud-bursting for more capacity: Quickly expand an on-premises deployment into the cloud by putting it behind a Traffic Manager profile. 当需要在云中获得额外的容量时,可以添加或启用更多终结点,并指定哪部分流量将流向每个终结点。When you need extra capacity in the cloud, you can add or enable more endpoints and specify what portion of traffic goes to each endpoint.

可以使用 Azure 门户、Azure PowerShell、CLI 和 REST API 配置权重。You can configure weights using the Azure portal, Azure PowerShell, CLI, or the REST APIs.

需要记住的一点是,DNS 响应将由客户端缓存。A point to remember is that DNS responses get cached by clients. 还将由客户端用来解析 DNS 名称的递归 DNS 服务器缓存。They're also cached by the recursive DNS servers that the clients use to resolve DNS names. 这种缓存可能会影响到加权流量分布。This caching can have an effect on weighted traffic distributions. 如果客户端和递归 DNS 服务器的数目较大,流量分布将按预期工作。When the number of clients and recursive DNS servers is large, traffic distribution works as expected. 但是,如果客户端或递归 DNS 服务器的数目较小,缓存可能会严重影响流量分布。However, when the number of clients or recursive DNS servers is small, caching can significantly skew the traffic distribution.

常见用例包括:Common use cases include:

  • 开发和测试环境Development and testing environments
  • 应用程序间通信Application-to-application communications
  • 目标用户群体较小、共享一个公用递归 DNS 基础结构的应用程序(例如,公司的员工通过代理进行连接)。Applications aimed at a narrow user-base that share a common recursive DNS infrastructure (for example, employees of company connecting through a proxy)

这些 DNS 缓存影响常见于所有基于 DNS 的流量路由系统,不只存在于 Azure 流量管理器上。These DNS caching effects are common to all DNS-based traffic routing systems, not just Azure Traffic Manager. 在某些情况下,显式清除 DNS 缓存可能会解决问题。In some cases, explicitly clearing the DNS cache may provide a workaround. 如果这不起作用,则可能更适合使用替代性流量路由方法。If that doesn't work, an alternative traffic-routing method may be more appropriate.

性能流量路由方法Performance traffic-routing method

跨国家或地区在两个或更多位置部署终结点可以提高应用程序的响应能力。Deploying endpoints in two or more locations across country or region can improve the responsiveness of your applications. 使用性能流量路由方法,你可以将流量路由到最靠近你的位置。With the 'Performance' traffic-routing method, you can route traffic to the location that is 'closest' to you.

Azure 流量管理器的“性能”流量路由方法

最靠近的终结点不一定是地理距离最近的终结点。The 'closest' endpoint isn't necessarily closest as measured by geographic distance. “性能”流量路由方法通过测试网络延迟来确定最靠近的终结点。Instead, the 'Performance' traffic-routing method determines the closest endpoint by measuring network latency. 流量管理器维护一份 Internet 延迟表,用于跟踪 IP 地址范围与每个 Azure 数据中心之间的往返时间。Traffic Manager maintains an Internet Latency Table to track the round-trip time between IP address ranges and each Azure datacenter.

流量管理器在 Internet 延迟表中查找传入 DNS 请求的源 IP 地址。Traffic Manager looks up the source IP address of the incoming DNS request in the Internet Latency Table. 然后,流量管理器在 Azure 数据中心内(该位置处理该 IP 地址范围的请求时具有最低延迟)选择一个可用终结点。Traffic Manager then chooses an available endpoint in the Azure datacenter that has the lowest latency for that IP address range. 然后流量管理器在 DNS 响应中返回该终结点。Then Traffic Manager returns that endpoint in the DNS response.

流量管理器工作原理中所述,流量管理器不会直接从客户端接收 DNS 查询。As explained in How Traffic Manager Works, Traffic Manager doesn't receive DNS queries directly from clients. 相反,DNS 查询来自客户端配置使用的递归 DNS 服务。Instead, DNS queries come from the recursive DNS service that the clients are configured to use. 因此,用于确定最靠近终结点的 IP 地址不是客户端的 IP 地址,而是递归 DNS 服务的 IP 地址。As such, the IP address used to determine the 'closest' endpoint isn't the client's IP address, but it's the IP address of the recursive DNS service. 此 IP 地址是客户端的适当代理。This IP address is a good proxy for the client.

流量管理器定期更新 Internet 延迟表,反映全国 Internet 的变化以及新的 Azure 区域。Traffic Manager regularly updates the Internet Latency Table to account for changes in the national Internet and new Azure regions. 但是,由于 Internet 上的负载会实时变化,应用程序性能也会随之变化。However, application performance varies based on real-time variations in load across the Internet. 性能流量路由不会监视给定服务终结点上的负载。Performance traffic-routing doesn't monitor load on a given service endpoint. 如果某个终结点变得不可用,则流量管理器不会在 DNS 查询响应中包括该终结点。If an endpoint becomes unavailable, Traffic Manager won't include it in the DNS query responses.

需要注意的要点:Points to note:

  • 如果配置文件包含同一 Azure 区域中的多个终结点,流量管理器会在该区域中的可用终结点之间均匀分布流量。If your profile contains multiple endpoints in the same Azure region, then Traffic Manager distributes traffic evenly across the available endpoints in that region. 如果想要在某个区域中采用不同的流量分布,可以使用嵌套式流量管理器配置文件If you prefer a different traffic distribution within a region, you can use nested Traffic Manager profiles.
  • 如果最靠近的 Azure 区域中的所有已启用终结点已降级,流量管理器会将流量转移到下一个最靠近的 Azure 区域中的终结点。If all enabled endpoints in the closest Azure region are degraded, Traffic Manager moves traffic to the endpoints in the next closest Azure region. 如果想要定义首选故障转移顺序,请使用嵌套式流量管理器配置文件If you want to define a preferred failover sequence, use nested Traffic Manager profiles.
  • 对外部终结点或嵌套式终结点使用“性能”流量路由方法时,需要指定这些终结点的位置。When using the Performance traffic routing method with external endpoints or nested endpoints, you need to specify the location of those endpoints. 请选择离部署最近的 Azure 区域。Choose the Azure region closest to your deployment. 这些位置是 Internet 延迟表支持的值。Those locations are the values supported by the Internet Latency Table.
  • 选择终结点的算法是确定性的。The algorithm that chooses the endpoint is deterministic. 同一个客户端重复发出的 DNS 查询会定向到同一个终结点。Repeated DNS queries from the same client are directed to the same endpoint. 通常,客户端在遍历时使用不同的递归 DNS 服务器。Typically, clients use different recursive DNS servers when traveling. 客户端可以路由到不同的终结点。The client may be routed to a different endpoint. 更新 Internet 延迟表也可能会影响路由。Routing can also be affected by updates to the Internet Latency Table. 这就是性能流量路由方法不保证始终将客户端路由到同一个终结点的原因。That's why the Performance traffic-routing method doesn't guarantee that a client is always routed to the same endpoint.
  • 更改 Internet 延迟表时,可能会注意到某些客户端被定向到其他终结点。When the Internet Latency Table changes, you may notice that some clients are directed to a different endpoint. 这种路由更改基于当前延迟数据,因此更加精确。This routing change is more precise based on current latency data. 进行这些更新很重要,可以确保在 Internet 持续发展的情况下“性能”流量路由的准确性。These updates are essential to maintain the accuracy of Performance traffic-routing as the Internet continually evolves.

地理流量路由方法Geographic traffic-routing method

流量管理器配置文件可以配置为使用地理路由方法,以便根据用户的 DNS 查询所源自的地理位置将用户定向到特定终结点(“Azure”、“外部”或“嵌套”)。Traffic Manager profiles can be configured to use the Geographic routing method so that users get directed to specific endpoints (Azure, External, or Nested) based on the geographic location their DNS query originates from. 使用此路由方法,可确保遵守数据主权授权、内容本地化和用户体验以及测量来自不同地区的流量。With this routing method, it enables you to be in compliance with data sovereignty mandates, localization of content & user experience and measuring traffic from different regions. 为地理路由分配配置文件时,与该配置文件关联的每个终结点都需要有一组分配给它的地理区域。When a profile is configured for geographic routing, each endpoint associated with that profile needs to have a set of geographic regions assigned to it. 地理区域的粒度可以是以下级别:A geographic region can be at following levels of granularity

  • 世界 - 任何区域World - any region
  • 区域分组 - 例如,非洲、中东、澳大利亚/太平洋等。Regional Grouping - for example, Africa, Middle East, Australia/Pacific etc.
  • 国家/地区 - 例如,爱尔兰、秘鲁、香港特别行政区等。Country/Region - for example, Ireland, Peru, Hong Kong SAR etc.
  • 省/自治区/直辖市 - 例如,美国加利福尼亚州、澳大利亚昆士兰州、加拿大阿尔伯达省等(注意:只有澳大利亚、加拿大和美国中的省/自治区/直辖市才支持此粒度级别)。State/Province - for example, USA-California, Australia-Queensland, Canada-Alberta etc. (note: this granularity level is supported only for states / provinces in Australia, Canada, and USA).

将一个或一组区域分配到某个终结点后,来自这些区域的任何请求都只路由到该终结点。When a region or a set of regions is assigned to an endpoint, any requests from those regions get routed only to that endpoint. 流量管理器使用 DNS 查询的源 IP 地址来确定用户查询的区域。Traffic Manager uses the source IP address of the DNS query to determine the region from where a user is querying from. 通常是作为本地 DNS 解析器的 IP 地址为用户进行查询。Commonly found as the IP address of the local DNS resolver making the query for the user.

Azure 流量管理器的“地理”流量路由方法

流量管理器读取 DNS 查询的源 IP 地址,并确定它所源自的地理区域。Traffic Manager reads the source IP address of the DNS query and decides which geographic region it's originating from. 随后,它会查找并查看是否存在此地理区域所映射到的终结点。It then looks to see if there's an endpoint that has this geographic region mapped to it. 此查找从最低粒度级别(即“省/自治区/直辖市”如果支持的话,否则为“国家/地区”级别)开始,一直向上查找,直到最高级别(即“世界”)。This lookup starts at the lowest granularity level (State/Province where it's supported, else at the Country/Region level) and goes all the way up to the highest level, which is World. 使用此遍历找到的第一个匹配项将被选定为要在查询响应中返回的终结点。The first match found using this traversal is chosen as the endpoint to return in the query response. 当与“嵌套”类型终结点匹配时,将基于其路由方法返回该子配置文件中的终结点。When matching with a Nested type endpoint, an endpoint within that child profile is returned, based on its routing method. 以下几点适用于此行为:The following points are applicable to this behavior:

  • 当路由类型是“地理路由”时,只能将一个地理区域映射到流量管理器配置文件中的一个终结点。A geographic region can be mapped only to one endpoint in a Traffic Manager profile when the routing type is Geographic Routing. 此限制确保用户的路由是确定性的,并且客户可以启用需要明确地理边界的方案。This restriction ensures that routing of users is deterministic, and customers can enable scenarios that require unambiguous geographic boundaries.

  • 如果用户区域列在两个不同的终结点的地理映射下,则流量管理器会选择粒度最低的终结点。If a user's region is listed under two different endpoints' geographic mapping, Traffic Manager selects the endpoint with the lowest granularity. 流量管理器不会考虑将请求从该区域路由到另一终结点。Traffic Manager won't consider routing requests from that region to the other endpoint. 例如,考虑包含两个终结点(终结点 1 和终结点 2)的“地理路由”类型配置文件。For example, consider a Geographic Routing type profile with two endpoints - Endpoint1 and Endpoint2. 终结点 1 配置为接收来自爱尔兰的流量,终结点 2 配置为接收来自欧洲的流量。Endpoint1 is configured to receive traffic from Ireland and Endpoint2 is configured to receive traffic from Europe. 如果请求来自爱尔兰,则始终会将它路由到 Endpoint1。If a request originates from Ireland, it's always routed to Endpoint1.

  • 由于一个区域只能映射到一个终结点,因此流量管理器不管该终结点是否处于正常状态都将返回响应。Since a region can be mapped only to one endpoint, Traffic Manager returns a response whether the endpoint is healthy or not.

    重要

    强烈建议客户使用地理路由方法将其与具有子配置文件(每个子配置文件中至少包含两个终结点)的“嵌套”类型终结点关联。It is strongly recommended that customers using the geographic routing method associate it with the Nested type endpoints that has child profiles containing at least two endpoints within each.

  • 如果找到终结点匹配项,但该终结点处于“已停止” 状态,则流量管理器会返回 NODATA 响应。If an endpoint match is found and that endpoint is in the Stopped state, Traffic Manager returns a NODATA response. 在这种情况下,将不在地理区域层次结构中的更高位置进一步查找。In this case, no further lookups are made higher up in the geographic region hierarchy. 当子配置文件处于“已停止” 或“已禁用” 状态时,此行为也适用于嵌套终结点类型。This behavior is also applicable for nested endpoint types when the child profile is in the Stopped or Disabled state.

  • 如果终结点显示“已禁用” 状态,则不会包含在区域匹配过程中。If an endpoint displays a Disabled status, it won't be included in the region matching process. 当终结点处于“已禁用” 状态时,此行为也适用于嵌套终结点类型。This behavior is also applicable for nested endpoint types when the endpoint is in the Disabled state.

  • 如果查询来自该配置文件中没有映射的地理区域,流量管理器将返回 NODATA 响应。If a query is coming from a geographic region that has no mapping in that profile, Traffic Manager returns a NODATA response. 这就是我们强烈建议你使用带有一个终结点的地理路由的原因。That's why we strongly recommended that you use geographic routing with one endpoint. 理想情况下,嵌套类型在子配置文件中至少有两个终结点,并分配有“世界”区域。Ideally of type Nested with at least two endpoints within the child profile, with the region World assigned to it. 此配置还可以确保处理任何不会映射到区域的 IP 地址。This configuration also ensures that any IP addresses that aren't map to a region are handled.

流量管理器工作原理中所述,流量管理器不会直接从客户端接收 DNS 查询。As explained in How Traffic Manager Works, Traffic Manager doesn't receive DNS queries directly from clients. DNS 查询来自客户端配置使用的递归 DNS 服务。DNS queries come from the recursive DNS service that the clients are configured to use. 这就是用于确定区域的 IP 地址不是客户端的 IP 地址,而是递归 DNS 服务的 IP 地址的原因。That's why the IP address used to determine the region isn't the client's IP address, but rather the IP address of the recursive DNS service. 此 IP 地址是客户端的适当代理。This IP address is a good proxy for the client.

常见问题解答FAQs

多值流量路由方法Multivalue traffic-routing method

多值 流量路由方法允许你在单个 DNS 查询响应中获得多个正常运行的终结点。The Multivalue traffic-routing method allows you to get multiple healthy endpoints in a single DNS query response. 此配置使得调用方在返回的某个终结点无法响应时能够通过其他终结点进行客户端重试。This configuration enables the caller to do client-side retries with other endpoints in case a returned endpoint being unresponsive. 此模式可以提高服务可用性,并降低与新 DNS 查询获取正常运行的终结点相关的延迟。This pattern can increase the availability of a service and reduce the latency associated with a new DNS query to obtain a healthy endpoint. 只有当所有终结点的类型都是“外部”并且指定为 IPv4 或 IPv6 地址时,多值路由方法才有效。MultiValue routing method works only if all the endpoints of type 'External' and are specified as IPv4 or IPv6 addresses. 当收到对此配置文件的查询时,会根据可配置的最大返回计数返回所有正常运行的终结点。When a query is received for this profile, all healthy endpoints are returned and are subject to a configurable maximum return count.

常见问题解答FAQs

子网流量路由方法Subnet traffic-routing method

“子网”流量路由方法可以将一个最终用户 IP 地址范围集映射到配置文件中的特定终结点。The Subnet traffic-routing method allows you to map a set of end-user IP address ranges to specific endpoints in a profile. 如果流量管理器收到该配置文件的 DNS 查询,它将检查该请求的源 IP 地址。If Traffic Manager receives a DNS query for that profile, it will inspect the source IP address of that request. 然后,它将确定映射到哪个终结点,并将在查询响应中返回该终结点。It will then determine which endpoint it's mapped to and will return that endpoint in the query response. 在大多数情况下,源 IP 地址是调用方使用的 DNS 解析程序。In most cases, the source IP address is the DNS resolver that is used by the caller.

可以将要映射到终结点的 IP 地址指定为 CIDR 范围(例如 1.2.3.0/24)或地址范围(例如 1.2.3.4-5.6.7.8)。The IP address to be mapped to an endpoint can be specified as CIDR ranges (for example, 1.2.3.0/24) or as an address range (for example, 1.2.3.4-5.6.7.8). 与终结点关联的 IP 范围在该配置文件中必须唯一。The IP ranges associated with an endpoint need to be unique within that profile. 地址范围不能与同一配置文件中不同终结点的 IP 地址集重叠。The address range can't have an overlap with the IP address set of a different endpoint in the same profile. 如果定义一个没有地址范围的终结点,则该终结点将用作回退终结点并从任何剩余的子网获取流量。If you define an endpoint with no address range, that functions as a fallback and take traffic from any remaining subnets. 如果未包含回退终结点,则流量管理器会针对任何未定义的范围发送 NODATA 响应。If no fallback endpoint is included, Traffic Manager sends a NODATA response for any undefined ranges. 强烈建议你定义一个回退终结点,以确保在终结点上指定所有可能的 IP 范围。It's highly recommended you define a fallback endpoint to ensure all possible IP ranges are specified across your endpoints.

子网路由可以用来为从特定 IP 空间进行连接的用户提供不同的体验。Subnet routing can be used to deliver a different experience for users connecting from a specific IP space. 例如,你可以将公司办公室的所有请求都路由到不同的终结点。For example, you can make all requests from your corporate office be routed to a different endpoint. 如果你尝试测试应用的内部唯一版本,此路由方法会特别有用。This routing method is especially useful if you're trying to test an internal only version of your app. 另一种情况是,你可能希望为从特定 ISP 进行连接的用户提供不同的体验(例如,阻止来自给定 ISP 的用户)。Another scenario is if you want to provide a different experience to users connecting from a specific ISP (For example, block users from a given ISP).

常见问题解答FAQs

后续步骤Next steps

了解如何使用流量管理器终结点监视开发高可用性应用程序Learn how to develop high-availability applications using Traffic Manager endpoint monitoring