Hello,
I'm having a Windows Server 2008 powered Network over here, where we are currently increasing redundancy everywhere.
The current Project is the DHCP, where only one Server is powering the whole network of about 300 Clients.
The Network ranges from 10.10.10.1 to 10.10.13.254, so should be able to cover the next years.
Now - when introducing split-range-DHCP - I'm thinking of an (almost) 50:50 split, as this would currently allow ANY DHCP to fail, without any limitation of Service.
Some questions:
I tested it with 2012 R2, it seems like Reservations are taking effect even if they are inside the "Exclusion" Range of an DHCP - right? (i.e. the second dhcp, having the exclusion range 10.10.10.10 - 10.10.11.254 can still give away the 10.10.10.19
ip, if there is a proper Reservation?)
Now I'm thinking of "swapping" the DNS Servers to have some sort of load-balancing between the Primary and secondary DNS-Server. While this seems to work nice in My homelab, just wanted to clearify that this won't cause any headache later.
After all, I'm thinking to deploy the following Setup:
DHCP1:
Range: 10.10.10.10 - 10.10.13.254
Exclusion: 10.10.12.1 - 10.10.13.254
Primary DNS: 10.10.10.1
Secondary DNS: 10.10.10.2
DHCP2:
Range: 10.10.10.10 - 10.10.13.254
Exclusion: 10.10.10.10 - 10.10.11.254
Primary DNS: 10.10.10.2 (note the swap)
Secondary DNS: 10.10.10.1 (note the swap)
Any thoughts? Does the Swap of the DNS-Servers Show the desired "Impact" in Terms of load-balancing between the DCs?
