[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-15

The preferred method for load balancing Microsoft Communications Server 2010 Edge Server traffic is to use DNS load balancing on both internal and external interfaces, but hardware load balancing will still be supported. For details, see Choosing a Topology.

DNS load balancing is now used on User and Director pools also, and if you have a pool of Edge servers, you need to consider how they will resolve the internal pool FQDN of the next hop server. The recommend approach to DNS name resolution is to configure the Communications Server 2010 Edge Server internal interface for either a perimeter or internal DNS server.