Managing Traffic Management Steering Policies

Policy Types

FAILOVER
Failover policies allow you to prioritize the order in which you want answers served in a policy (for example, Primary and Secondary). Oracle Cloud Infrastructure Health Checks are leveraged to determine the health of answers in the policy. If the Primary Answer is determined to be unhealthy, DNS traffic will automatically be steered to the Secondary Answer.
LOAD BALANCER
Load Balancer policies allow distribution of traffic across multiple endpoints. Endpoints can be assigned equal weights to distribute traffic evenly across the endpoints or custom weights may be assigned for ratio load balancing. Oracle Cloud Infrastructure Health Checks are leveraged to determine the health of the endpoint. DNS traffic will be automatically distributed to the other endpoints, if an endpoint is determined to be unhealthy.
GEOLOCATION STEERING
Geolocation steering policies distribute DNS traffic to different endpoints based on the location of the end user. Customers can define geographic regions composed of originating continent, countries or states/provinces (North America) and define a separate endpoint or set of endpoints for each region.
ASN STEERING
ASN steering policies enable you to steer DNS traffic based on Autonomous System Numbers (ASN). DNS queries originating from a specific ASN or set of ASNs can be steered to a specified endpoint.
IP PREFIX STEERING
IP Prefix steering policies enable customers to steer DNS traffic based on the IP Prefix of the originating query.

Typical Traffic Steering Scenarios

This section describes several typical scenarios for using Traffic Management Steering Policies.

Basic Failover

You can leverage Traffic Management Steering Policies to provide automated failover between primary and secondary servers.

Cloud Migration

Weighted load balancing supports controlled migration from your data center to Oracle Cloud Infrastructure servers. You can steer a small amount of traffic (1%) to your new resources in the cloud to verify everything is working as expected. You can then increase the ratios until you are comfortable with fully migrating all DNS traffic to the cloud.

Load Balancing Across Multiple Servers for Scale

You can configure load balancing pools of multiple servers. Traffic Management Steering Policies can automatically distribute DNS traffic across the set of servers. Health Checks may also be used and traffic will be automatically redirected to healthy servers, if a server is determined to be unhealthy.

Hybrid Environments

Since Traffic Management Steering Policies is an agnostic service, it may be used to not only steer traffic to Oracle Cloud Infrastructure resources, but can also be used to steer traffic to any publicly exposed (internet resolvable) resources, including other cloud providers and enterprise data centers.

Worldwide Geolocation Treatment

You can divide your global users into geographically defined regions (for example, state/province level in NA, country level for rest of world) and steer customers to specified resources based on their location. This helps to ensure global, high performing internet resolution, and supports functions such as ring fencing. For example, keeping traffic from China in China and block traffic outside of China into China.

Canary Testing

Leveraging IP Prefix steering, you can configure policies to serve different responses for your internal users versus external users.

Zero-Rating Services

ASN steering conditional steering based on the originating enterprise, mobile operator or other communications provider in support of various commercial agreements that may be in place. Essentially, preferred ASNs can be directed to free resources, while all other traffic can be directed to paid resources.

Using the Console

Managing Traffic Management Steering Policies

To create a Load Balancer policy
  1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Traffic Management Steering Policies.
  2. Click Create Traffic Management Steering Policy.
  3. In the Create Traffic Management Steering Policy dialog box, select Load Balancer.
  4. Enter the following information:

    • Policy Name: The unique name that identifies policy.
    • Policy TTL: The Time to Live for responses from the steering policy. If not specified, the system will set this value on the steering policy.
    • Maximum Answer Count: The maximum number of answers returned for the policy.
    • Answer(s): Answer pools contain the group of answers that will be served in response to DNS queries.

      • Name: A unique name to identify the answer. Avoid entering confidential information.
      • Type: The record type that will be provided as the answer.
      • RDATA: A valid domain name or IP address to add as an answer.
      • Weight: A number between 0 and 255 used to determine how often an answer is served in relation to other answers. Answers with higher values are more likely to be served.
      • Eligible: Select the check box to indicate that the answer is available within the pool to be used in response to queries. Alternatively, select Mark pool answers eligible or Mark pool answers ineligible from the Actions drop-down menu.
    • Attach Health Check: Select an existing Health Check to be included as part of the policy, add a new one, or select None.
    • Attach Domain(s): (Optional) The domain name and domain OCID you want to attach to the policy. Additional domains can be added in this section.
  5. Click Create Policy.

The system creates and publishes the policy.

To create a Failover policy
  1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Traffic Management Steering Policies.
  2. Click Create Traffic Management Steering Policy.
  3. In the Create Traffic Management Steering Policy dialog box, select Failover.
  4. Enter the following information:

    • Policy Name: The unique name that identifies policy. Avoid entering confidential information.
    • Policy TTL: The Time to Live for responses from the steering policy. If not specified, the system will set this value on the steering policy.
    • Maximum Answer Count: The maximum number of answers returned for the policy. For priority-based policies, the first valid answer is returned.
    • Answer Pool(s): Answer pools contain the group of answers that will be served in response to DNS queries.

      • Answer Pool Name: A user-friendly name for the answer pool, unique within the steering policy. Avoid entering confidential information.
      • Name: A unique name to identify the answer. Avoid entering confidential information.
      • Type: The record type that will be provided as the answer.
      • RDATA: A valid domain name or IP address to add as an answer.
      • Weight: A number between 0 and 255 used to determine how often an answer is served in relation to other answers. Answers with higher values are more likely to be served.
      • Eligible: Select the check box to indicate that the answer is available within the pool to be used in response to queries. Alternatively, select Mark pool answers eligible or Mark pool answers ineligible from the Actions drop-down menu.
    • Pool Priority: Failover priority rules specify the priority of answers that are served in a policy. If the primary answer is unavailable, traffic is steered to the next answer in the list.

      • Pool: Select the priority in which the answers are served.
    • Attach Health Check: Select an existing Health Check to be included as part of the policy, add a new one, or select None.
    • Attach Domain(s): The domain name and domain OCID you want to attach to the policy. Additional domains can be added in this section.
  5. Click Create Policy.

The system creates and publishes the policy.

To create a Geolocation Steering policy
  1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Traffic Management Steering Policies.
  2. Click Create Traffic Management Steering Policy.
  3. In the Create Traffic Management Steering Policy dialog box, select Geolocation Steering.
  4. Enter the following information:

    • Policy Name: The unique name that identifies policy. Avoid entering confidential information.
    • Policy TTL: The Time to Live for responses from the steering policy. If not specified, the system will set this value on the steering policy.
    • Maximum Answer Count: The maximum number of answers returned for the policy. For priority-based policies, the first valid answer is returned.
    • Answer Pool(s): Answer pools contain the group of answers that will be served in response to DNS queries.
      • Answer Pool Name: A user-friendly name for the answer pool, unique within the steering policy. Avoid entering confidential information.
      • Name: A unique name to identify the answer. Avoid entering confidential information.
      • Type: The record type that will be provided as the answer.
      • RDATA: A valid domain name or IP address to add as an answer.
      • Eligible: Select the check box to indicate that the answer is available within the pool to be used in response to queries. Alternatively, select Mark pool answers eligible or Mark pool answers ineligible from the Actions drop-down menu.
    • Geolocation Steering Rules: Geolocation steering rules specify the priority of answers that are served in a policy. If the primary answer is unavailable, traffic is steered to the next answer in the list. Additional rules and priorities can be added in this section.
      • Geolocation: Select a location that will be used to distribute DNS traffic.
      • Pool Priority: Select the priority in which the answers are served.
      • Global Catch-all: Adding a global catch-all allows you to specify answer pools for queries that do not match any of the specified rules you have added. Click Add Global Catch-all and select the pool priorities.
    • Attach Health Check: Select an existing Health Check to be included as part of the policy, add a new one, or select None.
    • Attach Domain(s): The domain name and domain OCID you want to attach to the policy. Additional domains can be added in this section.
  5. Click Create Policy.

The system creates and publishes the policy.

To create an ASN Steering policy
  1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Traffic Management Steering Policies.
  2. Click Create Traffic Management Steering Policy.
  3. In the Create Traffic Management Steering Policy dialog box, select ASN Steering.
  4. Enter the following information:

    • Policy Name: The unique name that identifies policy. Avoid entering confidential information.
    • Policy TTL: The Time to Live for responses from the steering policy. If not specified, the system will set this value on the steering policy.
    • Maximum Answer Count: The maximum number of answers returned for the policy. For priority-based policies, the first valid answer is returned.
    • Answer Pool(s): Answer pools contain the group of answers that will be served in response to DNS queries.
      • Answer Pool Name: A user-friendly name for the answer pool, unique within the steering policy. Avoid entering confidential information.
      • Name: A unique name to identify the answer. Avoid entering confidential information.
      • Type: The record type that will be provided as the answer.
      • RDATA: A valid domain name or IP address to add as an answer.
      • Eligible: Select the check box to indicate that the answer is available within the pool to be used in response to queries. Alternatively, select Mark pool answers eligible or Mark pool answers ineligible from the Actions drop-down menu.
    • ASN Steering Rules: ASN steering rules specify the priority of answers that are served in a policy. If the primary answer is unavailable, traffic is steered to the next answer in the list.
      • ASN: Enter an Autonomous System Number (ASN) that will be used to distribute DNS traffic.
      • Pool Priority: Select the priority in which the answers are served.
      • Global Catch-all: Adding a global catch-all allows you to specify answer pools for queries that do not match any of the specified rules you have added. Click Add Global Catch-all and select the pool priorities.
    • Attach Health Check: Select an existing Health Check to be included as part of the policy, add a new one, or select None.
    • Attach Domain(s): The domain name and domain OCID you want to attach to the policy. Additional domains can be added in this section.
  5. Click Create Policy.

The system creates and publishes the policy.

To create an IP Prefix Steering policy
  1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Traffic Management Steering Policies.
  2. Click Create Traffic Management Steering Policy.
  3. In the Create Traffic Management Steering Policy dialog box, select IP Prefix Steering.
  4. Enter the following information:

    • Policy Name: The unique name that identifies policy. Avoid entering confidential information.
    • Policy TTL: The Time to Live for responses from the steering policy. If not specified, the system will set this value on the steering policy.
    • Maximum Answer Count: The maximum number of answers returned for the policy. For priority-based policies, the first valid answer is returned.
    • Answer Pool(s): Answer pools contain the group of answers that will be served in response to DNS queries.
      • Answer Pool Name: A user-friendly name for the answer pool, unique within the steering policy. Avoid entering confidential information.
      • Name: A unique name to identify the answer. Avoid entering confidential information.
      • Type: The record type that will be provided as the answer.
      • RDATA: A valid domain name or IP address to add as an answer.
      • Eligible: Select the check box to indicate that the answer is available within the pool to be used in response to queries. Alternatively, select Mark pool answers eligible or Mark pool answers ineligible from the Actions drop-down menu.
    • IP Prefix Steering Rules: IP prefix steering rules specify the priority of answers that are served in a policy. If the primary answer is unavailable, traffic is steered to the next answer in the list.
      • Subnet Address: Enter a subnet address that will be used to distribute DNS traffic.
      • Pool Priority: Select the priority in which the answers are served.
      • Global Catch-all: Adding a global catch-all allows you to specify answer pools for queries that do not match any of the specified rules you have added. Click Add Global Catch-all and select the pool priorities.
    • Attach Health Check: Select an existing Health Check to be included as part of the policy, add a new one, or select None.
    • Attach Domain(s): The domain name and domain OCID you want to attach to the policy. Additional domains can be added in this section.
  5. Click Create Policy.

The system creates and publishes the policy.

To update a policy
  1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Traffic Management Steering Policies.
  2. Click the Policy Name you want to update. Policy information and a list of attached domains appear.

    Tip

    You can use search for a policy by name in the Search field. You can also use the Time Created sort filter to sort the policies chronologically in ascending or descending order.
  3. Click Edit.
  4. Make the needed changes, and then click Save.
To attach a domain to an existing policy
  1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Traffic Management Steering Policies.
  2. Click the Policy Name you want to update. Policy information and a list of attached domains appear.

    Tip

    You can use search for a policy by name in the Search field. You can also use the Time Created sort filter to sort the policies chronologically in ascending or descending order.
  3. Click Add Attached Domain(s).
  4. In the Add Attached Domain(s) dialog box, enter the domain and select a zone.
  5. Click Submit.
To edit an attached domain
  1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Traffic Management Steering Policies.
  2. Click the Policy Name you want to update. Policy information and a list of attached domains appear.

    Tip

    You can use search for a policy by name in the Search field. You can also use the Time Created sort filter to sort the policies chronologically in ascending or descending order.
  3. For the attached domain you want to edit, click the Actions icon (three dots), and then click Edit Attached Domain.
  4. In the Attached Domain(s) dialog box, enter the domain and select a zone.
  5. Click Save.
To delete a policy
  1. Open the navigation menu. Under Core Infrastructure, go to Networking and click Traffic Management Steering Policies.
  2. Select the check box for the policy you want to delete.
  3. Click Delete. The policy is staged for deletion.
  4. Click Publish Changes to delete the policy.
  5. In the confirmation dialog box, click Publish Changes.

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

For more information about managing steering policies using the API, see Traffic Management Steering Policies API Guide.

Use the following operations to manage your steering policies:

Use the following operations to manage your steering policy attachments: