Increase fault tolerance by splitting DHCP scopes
Applies To: Windows Server 2008 R2
It is a good idea to split a scope between two or three servers. In this way, one can handle DHCP traffic flood more easily. In addition, if a server fails, the network is not affected. An 80/20 split seems to offer the optimum benefit.
For example, consider a Class B scope 188.8.131.52 with address range from 184.108.40.206-220.127.116.11 and subnet mask 255.255.0.0. One setup would be to distribute the load between two servers (SRV1 and SRV2). SRV1 has a scope of 18.104.22.168-22.214.171.124 with a mask of 255.255.0.0. The exclusion range for this scope is 126.96.36.199-188.8.131.52. SRV2 has a scope of 184.108.40.206-220.127.116.11 with a mask of 255.255.0.0. The exclusion range for this scope is 18.104.22.168-22.214.171.124. A scope can also be divided between three servers in a similar way.
For a list of Help topics providing related information, see Recommended tasks for the DHCP server role.
For updated detailed IT pro information about DHCP, see the Windows Server® 2008 documentation on the Microsoft TechNet Web site.