Overview

For redundancy purposes, customers can set up a secondary site that is in a "passive" mode, IE no requests are currently being processed by that secondary site. One of the steps required during disaster recovery in order to complete "fail over" to a passive site is to flip a DNS switch that will publish the DNS Records for that site and un-publish the records of the original primary site. As RHCL manages these records, with the right controls , a user could trigger the failover to happen via their DNSPolicy 

Stories / Purpose

• Ensure High Availability for critical services/infrastructure by directing traffic to secondary site to healthy workloads, away from unhealthy workloads
• Optimization of Load Balancing for Round Robin DNS or Latency Based routing in the event of site failure
• Ability to failover to a second cloud service provider, datacenter or region
• Ability to still adhere to geo-specified routing for use cases that require data to remain within geography
• Ability to ensure DNS redundancy for internal/private traffic as well as public
• Ability to failover not only if a web service fails, but also database/data store failure as well