Also, remember the port flow:
| DHCP Option | Description |
|---|---|
| 015 | Specifies the connection-specific DNS domain suffix to be used by the DHCP client. |
| 119 | DNS Domain Search List option to specify the domain search list used when resolving hostnames with DNS. |
Assuming you are moving DHCP from DC1 to DC2
On DC1
netshDHCPserver \\dc1export c:\w2k3DHCPdb allOn DC2 (Assuming it is Server 2012)
C:\windows\system32\DHCP.netshDHCPserver \\Name or IP Addressimport C:\w2k3DHCPdbSimply setup your scope options for your new Windows Server 2012 DHCP server and then Authorize it within your domain and the migration is complete. (The GUI should give you a prompt on what to do)
Split scope (in IPv4) is not efficient. When one server is down, capacity is reduced by half and clients cannot renew with the remaining server. It forces clients using the failed server to go to DHCPDISCOVER and that may cause disruption to the clients as they will change IP address.
In IPv6, split scope works well because you have such huge IP address scopes.