I’m using BIND & ISC-DHCPD on a local linux server at home (will switch to KEA sometime) - My firewall dhcp server could not satisfy my requirements, especially wrt. dynamic dns updates.
IMHO a requirement for using DHCP, for “servers” is to:
MAC-lock the ip address to a “DHCP fixed IP”.
Will also make your firewall rules easier.
I think there are Pro’s & Con’s for using DHCP for “static” servers.
Pro’s:
1:
When moving from one subnet (vlan) to another.
You can predefine the new mac-locked ip in advance, and everything will be in place when moved.
We have often utilized that when working on remote systems, that didn’t have IPMI.
2:
You don’t have to fiddle with any IP settings in the GUI or resolv.conf.
Con’s
1:
DHCP was not made with redundancy in mind.
Meaning if your DHCP server goes down, you cant (easily) switch-in an up to date backup server,.
Well you can do some “pool splitting” in ISC-DHCPD, but then static reservations becomes a challenge.
I think that M$ DHCP can do something, but I use “Free FOSS” stuff.
2:
Remember to set your lease times long (I use 7 days)
Longer than ANY expected outage time on your DHCP server.
Ask me how i know
TIP:
1:
Don’t use DHCP on the PC you use to maintain the DHCP servers with.
2:
I have a disabled DHCP server configured on another linux server (small RasPi).
Just waiting to be activated if/when my primary server does down.
I have to remember to sync the dhcpd.conf from my primary server to the backup server … Once in a while (primarily for sync’ of reservations).
3:
Remember to hand out your preferred NTP server via DHCP too.
…
…
I’ll switch my TrueNAS’es to static, once i have my new Vlans in place.
TrueNAS Data Vlan & Protected IPMI (mgmt) Vlan.