Register DHCP Static Mappings in Unbound with dncmasq not working

Started by memzila, February 13, 2026, 03:25:27 PM

Previous topic - Next topic
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.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

February 13, 2026, 03:43:19 PM #2 Last Edit: February 13, 2026, 04:40:09 PM by DEC740airp414user
dnsmaq (under hosts) is setup with the same data as my Kea static mappings.

both products work.  I just prefer to use Kea.

DEC740 > USW-Pro-8-PoE> U6-Enterprise
Dec670. Retired / backup device

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 !! ;)
Weird guy who likes everything Linux and *BSD on PC/Laptop/Tablet/Mobile and funny little ARM based boards :)

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.

Quote from: nero355 on Today at 12:59:45 AM
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 !! ;)

Thanks. Will probably later try to configure it like this. As I currently not have the need for any advanced dhcp options, the KEA and Unbound Way with automatic registration of static dhcp entries in unbound is the more straightforward way at the moment

I need to participate here, because I'am struggling with the same issue. I have upgraded to 26.1 and now using KEA DHCP together with Unbound DNS, Dnsmasq DNS & DHCP is disabled.

From the link you provided I read that Dnsmasq is required as a connector. But in Unbound I have enabled Register DHCP Static Mappings and I thought this does exactly what I wanted: Having hosts which got a DHCP lease from KEA will be served via DNS. ... but it's not working.

Does KEA only have a hook towards Dnsmasq?

BR

Kea has a hook to Unbound for static mappings only. And none to DNSmasq if I am not mistaken.

For dynamic leases to be registered in DNS the current standard way is to use DNSmasq for DHCP and for DNS for the local domain. If you use Unbound as the client facing server and configure a forward for the local domain to DNSmasq of if you have DNSmasq answer to the clients and forward all recursive lookups to Unbound is a matter of taste, IMHO.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)