Activity 5.1: Using Round-Robin DNS for Multiple Clusters

You’re a network administrator for Blue Yonder Airlines, a worldwide airline with service to 27 countries. You recently implemented online reservations and ticketing services. Customers can now access the airline’s Web site, view information about services and schedules, and book their trips, purchase tickets, and request seat assignments. To ensure high availability, you’re using IIS on multiple servers that are configured as an NLB cluster. The Web site has been highly successful, and you now find that the cluster subnet is approaching saturation.

You decide to implement a second cluster on a different subnet. You plan to use round-robin DNS to resolve the DNS name (www.blueyonderairlines.com) to each cluster’s virtual IP address. The original cluster’s IP address is 10.1.0.1, and the new cluster’s IP address will be 10.2.0.1.

You decide to create a high-level sketch of the round-robin DNS and NLB cluster components in your network.

1. How should this configuration look?
2. What option other than round-robin DNS can you consider to balance the load between clusters?