Hello
I am beginning an AD consolidation exercise to collapse 4 domains into a new domain. I am looking to deploy a new Forest on the sites where the current forests are located.
My aim is to deploy DHCP servers for the new domain but I am not 100% sure of the best option to ensure that clients in the new domain receive DHCP information from the correct DHCP server.
Option 1 -I have read to create new VLANs for the clients and may then create an IP-Helper to only forward broadcasts to the IP of the DHCP server in the new domain. This would be ideal but not 100% sure if networks will create new VLANs
Option 2 - Add reservations for all clients. This will work but would require alot of effort as there will be 1000's of machines
Option 3 - What currently happens is that clients in the existing 4 domains hit a DHCP server and get an IP but as the 006 and 015 options are only set for the one domain, 3 of the 4 client domains have incorrect DNS information. I guess this means that alot of DNS forwarding requests is happening to resolve names in their local domain, Not a good solution but seems to work. Could this be an option?
Option 4 - Take option 3 and through DNS add additional suffixes - Again not really a good idea
Option 5 - Define DHCP User Classes. I have not tested and although this would ensure that the client only goes to the DHCP server with the matching class could the client still not go to one of the other domain's DHCP servers?
If anyone has experience or tips to share it will be good
Thanks