• You have at least two datacenters running the same application. The primary datacenter is always active. In case of failure/disaster the secondary/backup datacenter must kick in taking control and providing access to your application (disaster recovery)
  • Your application is mapped on a well-defined hostname (ie.
  • On the primary datacenter is running on IP a.b.c.d. One the secondary/backup datacenter is running on IP x.y.z.t
  • You need your clients traffic to be sent to the primary datacenter and, only in case of unavailability, be transparently sent to the secondary/backup datacenter


Logon now!



  • Use in priority balancing mode
  • Define one geohost that will be pointed by via a DNS CNAME record
  • Create two targets, one for each datacenter
  • Assign the relevant checks to each target
  • Configure the CNAME record on the primary DNS server that handles the domain

How to configure it:

  1. Register on and log on
  2. Select under which one of the available domains (,, …) you want to create your geohost. You can choose the domain you prefer, this is purely a “cosmetic” choice. Let’s choose
  3. Create your geohost: a geohost is the FQDN (Fully Qualified Domain Name) that your authoritative DNS will use as a CNAME for your application hostname (ie. Select “Priority” as your balancing algorithm. This will enable active-standby distribution of incoming traffic towards your datacenters.
  4. Define the first target: the target’s IP address is a.b.c.d and its priority must be 1
  5. Select checks to be performed on the first target
  6. Define the second target: the target’s IP address is x.y.z.t and its priority must be any number higher than 1. This allows the “priority” balancing algorithm to handle active-standby.
  7. Select checks to be performed on the second target
  8. Configure your authoritative DNS to use a CNAME record to have point to