This section describes how the GEO functionality typically works. Please note that within this configuration we are depicting the GEO LoadMaster as being located outside the data centers to make the flow clear. Though this can be the case, typically the GEO LoadMaster would be located within one or more of the data centers.

  1. A public client tries to connect to FQDN test.domain.com.
  2. The public client checks its local DNS.
  3. The local DNS forwards the request to the public DNS.
  4. The Public DNS forwards the request to GEO as it is the authoritative DNS for this record.
  5. GEO checks persistence and scheduling and decides which site to return.
  6. GEO returns the IP address for the client that made the request (in this case; the public DNS).
  7. The public DNS returns the results to the Local DNS.
  8. The local DNS returns the result to the client.
  9. The client connects directly to the site.