2. IP address ranges configured by DHCP in LAN cannot overlap. In this way, the DHCP load can be balanced at ordinary times, and the other one can be used as a backup when problems occur.

Please refer to the following article for details.

DHCP cluster

In the current network, DHCP (Dynamic Host Allocation Protocol) is very important, especially when it needs to be used with Win2K's domain name service. But unlike WINS and DNS, DHCP lacks the ability to share or replace databases. Each DHCP server provides services independently, so using multiple DHCP servers may lead to resource occupation or overlap. When a DHCP server is shut down, the backup DHCP server may provide two IPS for a client computer.

The network administrator configures multiple DHCP servers to cooperate with multiple WINS servers to achieve fault tolerance and faster access. But just as running multiple WINS servers will increase risks and management difficulties, using multiple DHCP servers will have the same consequences.

The traditional way to deal with the simultaneous operation of two DHCP servers is to use 80/20, with one providing 80% IP of the mask setting and the other providing 20% IP without overlapping, so that after the first server goes down, the second server can provide IP distribution service.

Compared with the above 80/20 method, clustering DHCP database is a truly correct solution to provide fault tolerance. With clustering, all valid addresses can be configured in one database, so once one server fails, another server will immediately take over the DHCP service. Of course, users can still keep the traditional 80/20 method to improve fault tolerance.

Configure DHCP cluster

Configuring a DHCP cluster is similar to configuring a WINS service cluster. DHCP service resources require the following conditions: physical disk, IP address and network name.

PAF . net/Class/DHCP/06 10 13 14584082874820 . html