Skip to main content

Route DNS traffic

Use DNS response policies to control which destinations are returned for supported records. Regional views provide answers for different geographic regions, while simple failover uses destination priority and health to influence selection.

Start with a working record configuration, then choose the behavior you need. Review the applicable limits and test the resulting answers before relying on the policy for production traffic.

Provide region-specific answers

Use Regional views when different regions should receive different DNS responses.

The article explains supported regions, the global default, regional overrides, and the effect of disabling records. A records provide an example workflow, but other supported record types can also have regional values.

Review both the global configuration and regional overrides when investigating an unexpected answer.

Configure destination failover

Use Simple failover when response selection should account for destination priority and health.

The article explains destination states, target limits, inactive failover, and how responses are selected when some or all destinations are unhealthy.

Adding multiple addresses to a standard record does not, by itself, enable health monitoring or automatic failover. Configure the policy required for the intended behavior.

Combine regional views and failover

Regional views and simple failover can work together. Review how failover behaves within the regional configuration, including the destinations available to each region.

Test the cases your service needs to handle, such as an unavailable preferred destination or a region without an explicit override.

Also account for TTL: a newly selected DNS response does not replace answers already cached by clients and resolvers.

For the underlying record fields, see Manage DNS records. For nameserver, delegation, and synchronization checks, see DNS zone health.