The brains behind the balancing: a rules-based order that starts at the network/subnet level
Organizing sites using DNS segmentation and zero-trust DNS methods provides critical controls for handling traffic and implementing security policies suited to different client types (e.g., IoT). Segmentation enhances routing, enforces access controls, and safeguards against malicious activity. Zero-trust DNS verifies that devices communicate only with authorized endpoints, enabling real-time threat identification and proactive policy enforcement.
Migration is easy. NetOps teams with existing DNS business logic organized by site, country, region, city, or other breakout typologies can transfer that logic to Edge DNS GSLB. Rules are implemented at the network level to base distribution on subnets, with domain-level exceptions as needed.

Figure 1. DNS GSLB network/subnet methodology fits any existing network typology

Figure 1. DNS GSLB network/subnet methodology fits any existing network typology
Mechanisms and strategies
Use cases
1. Multiregion disaster recovery
Ensure availability for critical services (e.g., app.example.local) across regions with routing that adapts to network conditions. Define resolution logic based on consumer and producer subnet groupings to match current infrastructure.

Figure 2. Normal operations with primary endpoints online
During normal operations, consumer networks (e.g., Subnet A and Subnet B) resolve to healthy primary production networks (Subnet M and Subnet N). Responses are optimized and distributed based on business-aligned policies (geographic affinity, capacity, performance).

If Subnet M and Subnet N become unavailable (e.g., outage, DDoS), DNS GSLB dynamically reroutes traffic to Subnet O in another city or cloud region—without waiting for TTLs or manual reconfiguration.

For partial failures (e.g., only Subnet N down), traffic shifts to Subnet M immediately. Once health checks confirm recovery, traffic rebalances according to the original priority logic—no manual adjustments required.
A single gateway or shared service fronting multiple applications can be health-checked and governed by a single GSLB rule to redirect all dependent applications if the gateway becomes unavailable.
2. Per-application multinetwork delivery
Define precise, domain-specific routing policies for each application—even within the same consumer network block—so different applications can use distinct network paths and priorities without extra infrastructure.

Example: All queries from IP Block A route to Subnet M by default, but app.example.local is overridden to Subnet P.

Example: In IP Block A, dev.example.local routes to Subnet P (performance/proximity), while hr.example.local routes to Subnet M (compliance/data residency).
This enables nuanced, application-level routing across shared environments with centralized visibility and control.