Does ISC’s KEA support Dynamic DNS for Active Directory-based DNS on OPNsense?

Started by loaderladdy, November 01, 2026, 05:15:26 PM

Previous topic - Next topic
KEA's documentation on integration with AD DNS, found here GSS-TSIG Integration with External Systems states the following:

QuoteKea provides support for DNS updates, which can be protected using Transaction Signatures (or TSIG). This protection is often adequate. However, some systems, in particular Active Directory (AD) on Microsoft Windows servers, have chosen to adopt a more complex GSS-TSIG approach that offers additional capabilities, such as using negotiated dynamic keys.

Kea supports GSS-TSIG to protect DNS updates sent by the Kea DHCP-DDNS (D2) server in a hook, called libddns_gss_tsig.so.

However, searching my OPNsense filesystem I cannot find Kea's hook file "libddns_gss_tsig.so"

What I want to know is there a way to install the necessary Kea GSS-TSIG file on OPNsense?.

I use my OPNsense device as the front door for my homelab, and as I work with AD my homelab has AD installed, so integrating Kea DDNS with AD DNS would be great.

I know Windows DHCP supports DDNS, but I wanted a rock-solid solution that keeps my household happy, and running Windows DHCP doesn't fit that desired outcome after a power cut.

Any help or advice on this is greatly appreciated.

Quote from: loaderladdy on November 01, 2026, 05:15:26 PMsearching my OPNsense filesystem I cannot find Kea's hook file "libddns_gss_tsig.so.What I want to know is there a way to install the necessary Kea GSS-TSIG file on OPNsense? "

it is not installable as a package .

OPNsense package isn't built that way..there is no file to copy in

Let Windows clients self-register via option 81 (Client FQDN), or move only D2 (kea-dhcp-ddns) to a Linux VM built with Kerberos enabled.

Don't use a shared-key TSIG on an AD-integrated zone set to Secure only

On the power cut: the DC is the real dependency, not the DHCP host --> the clients can register themselves once it's up
Hardware: N5105 Intel Celeron  
                       OPNsense | Home Lab | Linux & Home Automation
                               "Secure the network, automate the rest."

Thanks for your reply, which is much appreciated.

FYI, what I was doing in the background was taking the various OPNsense tools and repositories from github and installing them on a FreeBSD Hyper-V guest, under the watchful eye of Copilot.  We found that the various package components are already built into the FreeBSD repositories.  So Copilot helped me to create the missing Kea components, which I managed to do.  Another advantage is that ISC have made these Kea components free to use, ISC used to require an ISC business licence, but not anymore.

I realise that OPNsense's KEA build is downstream of FreeBSD's build so, maybe, one day Kea will be updated to include these enhancements to Kea for its DDNS capability.

One thing I did do is turn of Secure updates on ADDS DNS and I can report this is working without populating the KEA TSIG config elements, which are now empty.  I know it is less than ideal for my internal AD DNS server to be accepting insecure updates, but it's my risk I guess and have accepted it.

Many thanks