At block 210, a transition to a different version of the load balancing service may occur. The transition may require the number of load balancing nodes to change from M to N, where N may be either less or more than M, due to changes in the traffic behavior of the service. Further, the number of back-end pool nodes in the pool may change from W1 to W2. At block 212, the configuration of DNS 106 may be updated. For example, a new public IP address 122, 9.0.0.2, may be assigned to the example.com entry 120. Further, the load balancing information for W2 servers 110A-W2 may be populated to the N (out of M) load balancing nodes 108A-N. A new rule 124, or set of rules, only for IP address 126, 9.0.0.2, may be created in traffic distributors 104. The rules spread traffic to the N load balancing nodes, again using, for example, modulo operation, with a modulus N. Likewise, DNS entry 112 may be updated with the new IP address 122, 9.0.0.2, and the old IP address 114, 9.0.0.1, may be removed. Alternatively a new DNS entry 120 including the new IP address 122, 9.0.0.2, may be created, and the old DNS entry 112 including the old IP address 114, 9.0.0.1, may be removed.

Optionally, load balancing nodes 108A-N may be configured not to accept new connections on the old IP address 114, 9.0.0.1. Alternatively, load balancing nodes 108A-N may be configured to accept new connections on the old IP address 114, 9.0.0.1.