Topic Last Modified: 2012-10-22
A scaled Director pool, where there are more than one Director deployed to handle additional capacity and to provide high availability, requires load balancing to distribute client and server communication to all members of the pool. A Director hosts web services much like a Front End pool. To provide the load balancing, you can use either hardware load balancing or domain name system (DNS) load balancing and hardware load balancing. Hardware load balancing is required for the web services, and DNS load balancing alone does not provide the capabilities required for the web services.
The following topics describe the planning considerations for deploying a Director pool using DNS load balancing in conjunction with hardware load balancing. If you intend to use hardware load balancing, but not DNS load balancing for the Director pool, see the topic Scaled Director Pool - Hardware Load Balancer that describes the planning requirements for that topology.