Установка сервера DHCP как обработка отказа

I think you're on the right track with what you want to do here. You haven't specified which version of Windows Server you are running so I am going to assume Windows Server 2008 R2 for the purpose of my response.

The first step would be to install the DHCP role on your 2nd Domain Controller. There is a good walkthrough with the steps necessary to do this at howtogeek but the basic steps are:

Open "Server Manager" > Right-click *"Roles"** > Select "Add Roles"

Add the "DHCP Server" Role listed under "Server Roles" and then you'll need to configure the settings, which brings us to the next part of your question. How to beset setup multiple DHCP servers in a failover configuration.

Using a split scope is an option for this, but it is not the only option. In fact, you really have three options:

1.Split Scopes - Splitting your DHCP scope between multiple servers

Advantages:

• Cheaper than other solutions as it does not require the purchase of an external disk system for clustering
• You're protected from database corruption because if either of your DHCP servers becomes unavailable due to a DB corruption, the other one can step right in and server DHCP while the down system is being repaired

Disadvantages

• In the event of an outage of one of your DHCP servers (whether due to system upgrades or an unplanned outage), you'll be limited to half of the DHCP scope (assuming you do a 50/50 split). If IP availability is not a concern, this may not be a big deal.

2.DHCP Clusters - Multiple servers acting together to server IPs in the same DHCP scope

Advantages

• Easily administered from the Cluster Administrator MMC
• Systems can be upgraded while online
• If a single server in the DHCP Cluster is offline, 100% of the DHCP scope is still available

Disadvantages

• If the clustered DHCP database becomes corrupted, the DHCP service will be unusable until repaired (translation: single point of failure)

3.DHCP Standby Server - In this configuration, your secondary DHCP server would be configured exactly like the primary, but you would leave the service disabled until it was needed due to an outage of the primary system

Advantages

• You get the full DHCP scope availability that the clustered solution offers while still keeping the minimal hardware costs that are associated with the split scope definition

Disadvantages

• Manual intervention is required to start the service in the event of an outage of your primary DHCP server
• You will run into DNS record ownership issues if DHCP is configured to update DNS records due to them being own by the failed DHCP server
• Extra network bandwidth is required when first bringing the secondary server online due to it having to rescan the network to assign IPs (if you go this route, I highly recommend enabling conflict detection on your secondary DHCP server)

Recommendation: My recommendation for you would be to go with the Split Scope solution you've already been leaning toward, as long as you have enough available IPs that half of the total DHCP scope would be sufficient for your needs (so as not to run into any problems if one of the servers is offline).

Directions: Configuring Split Scopes

• Open the DHCP Microsoft Management Console (MMC) snap-in.
• In the console tree, double-click the DHCP server you want to configure.
• Right-click IPv4 and then right-click the scope you want to split.
• Click Advanced and then click Split-Scope.
• Follow the instructions in the DHCP Split-Scope Configuration Wizard.