Creating an IP Prefix Steering Policy

Create an IP prefix traffic management policy that steers DNS traffic based on the IP prefix of the originating query.

See Traffic Management for a feature overview and more information about IP prefix steering policies.
    1. Open the navigation menu and click Networking. Under DNS management, click Traffic management steering policies.
    2. Under List scope, select the compartment in which you want to create the policy.
    3. Click Create traffic management steering policy.
    4. For Policy type, select IP prefix steering.
    5. Enter the following information:
      • Policy name: A unique name that identifies policy. Avoid entering confidential information.
      • Policy TTL: The time to live for responses from the policy. If not specified, the system sets this value.
      • 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 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 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. Or, click the Actions menu (Actions Menu) and select Mark pool answers eligible or Mark pool answers ineligible.
      • 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 used to distribute DNS traffic.
        • Pool priority: Select the priority in which the answers are served.
        • Global catch-all: Adding a global catch-all lets you specify answer pools for queries that don't 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 that you want to attach to the policy. You can add more domains as needed.
    6. (Optional) Click Show Advanced Options: to apply tags to the policy.
      If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, skip this option or ask an administrator. You can apply tags later.
    7. Click Create policy.
  • Use the steering-policy create command and required parameters to create an IP Prefix steering policy:

    oci dns steering-policy create --compartment-id compartment_id --display-name policy_name
    --template ROUTE_BY_IP  ... [OPTIONS]

    For a complete list of flags and variable options for CLI commands, see the CLI Command Reference.

  • Run the CreateSteeringPolicy operation to create an IP Prefix steering policy. Specify the TemplateType parameter as ROUTE_BY_IP.

    See Traffic Management Steering Policies API Guide for more information on using the API to create steering policies.