Monday, November 25, 2019

DHCP Server part of AD or hardware - what is best practices

A network I am walking into after the previous IT was fired (not important), and I was in discussing what was there vs what we are going to replace, as its in need of an upgrade as well.

Their existing system is an AD server, which is fine, but with DHCP server on it as well. They have made a range, lets say 192.168.0.1/24 and then when they added a machine they wanted static, they would add to exclusion - then its static... I guess. Ive never seen it that way.

What the discussion turned to was replacing the main firewall (the plan anyhow) and having it be the DHCP server, and serving a range, say 192.168.0.150-225 and then static IP'ing the printers and servers outside of that range.

The question came up - which is best practices? Good question to debate I thought. The AD server is a must, and we dont want to change that, but leave DHCP and DNS on that, or move to appliance?



No comments:

Post a Comment