Multiple DNS names and IP address to make load balancing more efficient in an Exchange CAS Array

view full story

http://serverfault.com – The tl;dr problem The CAS server occasionally gets one or two NAT'ed IP addresses that have several hundred users behind it. That is bad for scalability. The tl;dr solution Have the NAT'ed outlook clients connect to more than one DNS name/IP destination. Use this in the load balancer, and the NAT issue is reduced. More information A majority of our Exchange customers use RPC/HTTPS and Outlook Anywhere. Many of our clients are grouped in the hundreds behind a single NAT address. This results in the load balancer sending large NAT'ed user populations to the same CAS server. The CAS se (HowTos)