Details per system are available here:

The following example shows how to create a server with a different Domain name to be used to test aiCache without requiring a local change of host file, i.e. aicache.xyz.com that answers to www.xyz.com.com

If you have an installation with a load balancer this is the easiest method to take aiCache live.

We recommend putting the aiCache instance into rotation with a small percentage of the requests.  Let aiCache run for some time keeping an eye on the caching statistics.  You can gradually increase the percentage of traffic.  If you see any issues you can take aiCache out of rotation to tune the configuration. You can opt to keep aiCache in a load balanced environment or after a period move the DNS records.

PRS: Ability to test gradually

PRO: Ability to instantly remove traffic if there is an issue

CON: Load balancer introduced an additional hop and complicates traffic flow 

Pointing DNS IN A record to aiCache instance ip address

PRO: All traffic will go directly to aicache instances (no extra hop), also there are no additional costs

CON: if something goes wrong it will take some time to fall back to original DNS IP address mapping 

(DNS servers worldwide do caching of name-ip records)

aiCache can be configured using geo-routing such as provided by Dyn.com.  This allows you to quickly move traffic between one or more aiCache servers and/or Origin servers.

Please see section on DCC's for more detail.