As dnsmasq is now the default DHCP Service I have switched from KEA to dnsmasq.
But it looks like now the registering of static DHCP Mappings is no longer working.
Is this intended? Do I have switch back to KEA?
Or will this function that static mappings from dnsmasq are created in Unbound will come in the future?
You need to use DNSmasq for DNS, too.
dnsmaq (under hosts) is setup with the same data as my Kea static mappings.
both products work. I just prefer to use Kea.
Sorry. A little more precise. The dns registration of static dhcp entries in unbound is not working.
Ok. Then if I understand correctly.
When I want the more advanced features from unbound like dns overrides or query forwarding for as example a nextdns integration and I like that the static dhcp entries are registered in unbound, the only way is to actual use KEA?
Quote from: memzila on February 13, 2026, 04:29:44 PMthe only way is to actual use KEA?
No.
Please read https://docs.opnsense.org/manual/dnsmasq.html#dhcpv4-with-dns-registration carefully and adjust your configuration accordingly !! ;)
You're basically on the right track. If you want Unbound to handle advanced features like DNS overrides, forwarding (for something like NextDNS), and also automatically register static DHCP leases, then Unbound needs to be the resolver that receives those host entries. With the legacy ISC DHCP, that integration can be limited or inconsistent depending on setup. KEA is designed to integrate more cleanly in newer stacks, especially in systems like OPNsense, where KEA can dynamically update Unbound via proper hooks. So yes, if automatic registration of static DHCP entries in Unbound is important alongside advanced DNS features, moving to KEA is usually the cleaner and more reliable approach.