+ 0 Votes I'd say a server WhoFsckingCares December 27, 2012 at 4:57am PST I like a router to do routing, and a firewall to do firewalling, so I'd put the DHCP function on a server. From a security perspective, an attacker hits your outside router or your firewall first, so if that's compromised they now own your DHCP as well. Put it on a server and it's one more layer to penetrate. From a management perspective, both Windows DHCP and the Linux dhcpd (via Webmin) have pretty GUIs, so you can manage DHCP a little easier if it's on a server. And from a reliability perspective, I believe that both Windows 2012 Server and dhcpd support true redundancy in DHCP.