I had started to go the route of kea when ISC said they were going to deprecate isc-dhcpd. Maybe I have too many obscure options in my configuration but I foun

I had started to go the route of kea when ISC said they were going to deprecate isc-dhcpd. Maybe I have too many obscure options in my configuration but I found the configuration to be a bit complex and bloated in my opinion for a home DHCP server. Instead I went the route of dnsmasq and the end result was an even smaller and simpler configuration. It also has a tiny memory footprint as compared to isc-dhcpd and isc-kea. I would probably use kea in a corporate environment as it is modular and configuration management frameworks like Anisble could perhaps hide the complexity. Here is the memory usage for dnsmasq. I do not recall the exact memory footprint kea was using but I do remember it was bigger a few MB. This is probably not a big deal for most people but for a home setup I like to keep things lean. Private + Shared = RAM used Program 56.0 KiB + 53.5 KiB = 109.5 KiB init 364.0 KiB + 31.5 KiB = 395.5 KiB dnsmasq Configuration line count including static reservations: grep -Ev ^# /etc/dnsmasq.conf | wc -l 48 With kea I had to enable multiple modules and it the configuration looked more like the source code of a program to me. This is probably fine for developers. For me dnsmasq is just one tiny file that is very easy to read.