1. Scaling Network Load Balancing Clusters
DNS rotates list for each query which statically load MybigWeb IN A Network Load Balancing clusters have a maximum of 32 hosts, and all of the hosts must be on the same subnet.

2. Network Load Balancing clusters have a maximum of 32 hosts, and all of the hosts must be on the same subnet. If a cluster cannot meet the performance requirements of a clustered application, such as a Web site, because of a host count or subnet throughput limitation, then you can use multiple clusters to scale out further.
Combining round robin DNS and Network Load Balancing results in a very scalable and highly available configuration. Configuring multiple Network Load Balancing clusters on different subnets and configuring DNS to sequentially distribute requests across multiple Network Load Balancing clusters can evenly distribute the client load that is distributed across several clusters. When multiple Network Load Balancing Web clusters are configured with round robin DNS, the Web servers are made resilient to networking
infrastructure failures also. For example, as shown in the graphic where arrows 1, 2, 3 and 4, 5, 6 represent a client URL query, DNS response, and cluster connection request, notice that each DNS entry is a reliable cluster and loss of an individual cluster member does not result in clients being issued nonfunctional IP addresses.

3. When you use round robin DNS in conjunction with Network Load Balancing clusters, each cluster is identified in DNS by the cluster virtual IP. Because each cluster is automatically capable of both load balancing and fault tolerance, each DNS-issued IP address will function until all hosts in that particular cluster fail. Round robin DNS enables only a limited form of TCP/IP load balancing for IP-based servers when used without Network Load Balancing. When used with multiple individual hosts, such as Web servers, round robin DNS does not function effectively as a high-availability solution. If a host fails, round robin DNS continues to route requests to the failed server until the server is removed from DNS.