asked on
Should I add the role of DHCP server to Windows Server 2019
I am setting up a new Windows 2019 Server for a customer. The way I was taught in the past was to add the role of DNS server to the DC and use the router for the DHCP to the PCs. I have done it successfully on several servers but it seems convoluted and possibly not correct and efficient. I do have one customer where the DC is both the DHCP server and DNS server and have not had any issues. The DNS is configured properly with the interfaces and forwarders and DHCP turned off in the SonicWall. DHCP is configured with the scope and all of the correct parameters. I would like to get some opinions as to which way to go. It seems to me it would be best practice to allow the DC to do both. What are the pros and cons (if any) using this method?
Thank you in advance,
Phil
Thank you in advance,
Phil
Microsoft Server OSWindows OSDHCPDNS
Last Comment
Phil Rine
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
If I opted not to have the DC as the DHCP server (which I am not leaning towards), would it be better to remove the DNS role from the DC and let the router manage it?
No, the AD relies on DNS, where would you put the DNS, often routers provide caching type DNS, you need an authoritative DNS for your AD zone.
Dhcp, DNS are not a resource intensive role.
Usually, one offloads roles that consume resources .
Dhcp, DNS are not a resource intensive role.
Usually, one offloads roles that consume resources .
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks to all. I am going to doing this on Friday and will post the outcome.
ASKER
Thank you to all that helped me on this issue. I installed the DHCP role on the DC. Everything seemed to be going great except that when I restarted any computer it would not get an IP address or be listed as an attached device. I made the changes in the server and the router/firewall but still nothing. I thought I would lose my mind until I realized that I skipped a step due to my inexperience with this. I never activated the DHCP. Pretty embarrassing, especially after spending a couple of hours trying to figure out why. Once done, everything was a smooth as could be. I will never forget that for the next time!
Ad dhcp has to be authorized and scope activated.
ASKER
Yes. I found that out the hard way! Inexperience.