This configuration example covers global server load balancing
of multiple distributed servers using the edgedirector
geobalancing dns service. To avoid publishing details that might
apply to servers belonging to other parties, the domain name
used in the example will be example.com and the addresses used
will be private ip ranges. This practice is in accordance with
the recommendations of the IETF as published in various RFC's.
example.com wants to ensure visitors from around the globe are
served by the closest server. Multiple servers are in place at
geographically distributed data centres. The site is published
as example.com and www.example.com 1. Create one example.com
address record for each distributed server ip address. 2. Create
one alias record for www.example.com pointed at example.com with
a matching ttl. The www.example.com alias record will follow the
example.com target automatically. 3. Set the geo coverage for
each server according to physical location. Leave the global
coverage enabled for al