pfSense

We now have a brand new integration with Kea that solves all of these issues and more. We now support both DHCPv4 and v6 DNS registration with unbound. Additionally, it is now possible to turn on registration globally for all subnets or override the registration policy per subnet. This allows for both per-subnet opt-in (aka global disable policy) or opt-out (aka global enable policy). It's very flexible.

The domain name that is appended to each lease hostname for registration is selected according to the following rules(first match wins).

1. Does the DHCP response contain a domain-name option? If so, use it.
2. If no domain-name option is present in the response, or we are handling a DHCPv6 lease, check it the response contains a search-domain option. If so, use the first one as multiple could be specified.
3. Use the system domain name.

There are a few things that still need some polishing, Christian is aware, some require changes in Kea that area already known and still pending. Notably:

• Lease entries synchronized from HA primary to secondary are not added to Unbound on secondary
• Lease entries are not added to Unbound at startup for existing leases, only during lease events
• Static mappings are only added to Unbound when a client requests a lease. If an entry is used as a placeholder for a static/non-DHCP client which never requests a lease, it does not get added to Unbound