Re: DNS & DHCP

<snip> Thank you for the extensive answers :) This is the one reason I’m dismissing NSD, though I’ve tried to make it fit, but I’m in need of : - DHCP (preferably a PostgreSQL back-end) * DHCPv6 - DDNS updates from DHCP - Caching resolver with routing/split horizon/filtering options - Radius Reason: in my ProxMox cluster(s) I’m constantly having to handle DHCP statics/reservations, which I previously did (meticulously in pf/OPNSense’s DHCP server pages). Moving to FortiGate for my firewalling, this now became a tad more laborious inside their GUI, which is that tipping point to start looking at something to do the DHCP+(dynDNS) for the internal network, not to mention I need a caching resolver too to handle a tad of traffic, but I’m not into deploying big VMs just for that. I At the time I started writing this email (Satruday) I was still between Yadifa & Knot, HOWEVER: I since then got to know of KNOT-Resolver, thus, I’m going to deploy Knot Auth, knot-resolver for DNS and Kea+Stork for DHCP+DDNS, all back-end with Postgresql as far as possible :) (Yes, knot-resolver seems a tad more involved, as you now have a LUA embedded resolver to do fancy stuff)