Performance based traffic steering.
ITO Pools use real-time monitoring metrics to steer traffic to the fastest responding endpoint(s). You can use ITO pools to:
All Failover decisions are informed by real-time information from our Sonar monitoring beacon. As soon as an IP is offline or underperforming, DNS automatically moves your traffic over to your backup IP. Sonar then monitors your old IP and will failback your traffic when it becomes available.
Our Enhanced Failover solutions now have the ability to be combined with our Global Traffic Director and Round Robin (pools) features for additional redundancy and more precise routing configurations.
Enhanced DNS Failover offers three different ranking modes. Rankings determines the order the backup IP addresses will be served when the primary IP in unavailable.
|Ranking Mode||Description||How It Works|
|Normal||Always lowest levels||Attempt to keep the IP address to the most preferred system in the list.|
|Off On Any Failover||Move to an active IP||Turn off failover after any failover.|
|One Way||Move to higher levels||Only failover your domains to IPs that are further down the list. For example, IP #1 will failover to #2, and #2 will failover to #3, but it will never go back to #1 unless manually changed.|
Constellix uses Record Pools to load balance across multiple endpoints. Pools work with the following services:
You can configure pools with A, AAAA, and CNAME records.
Distribute your traffic load evenly across multiple servers.
Round Robin works by responding to DNS requests with not just one IP address, but with a list of IP addresses of several servers that host identical services.
We like to think of round robin as a rotor: as in round robin rotates DNS records for each incoming DNS request, resulting in each visitor being served by a different server.
Weighted Round Robin gives you a clean and effective way to distribute varying traffic loads across available resources.
It's different from traditional Round Robin in that you can specify unequal weights for each IP. For example: The "weight" can be determined by the capacity of one server in comparison to the other servers in the pool.
You can configure Weighted Round Robin with A, AAAA, and CNAME record pools.