Bug #3284
closed
dhcpleases cannot identify domains set in DHCP server settings, breaks dnsmasq lookups
0%
Description
dhcpleases is started with the domain suffix set to the domain of the pfsense installation. DHCP servers on individual interfaces can specify their own domain. If DHCP lease registration is enabled for dnsmasq, the "global" domain suffix is copied into /var/etc/hosts for each entry in /var/dhcpd/var/db/dhcpd.leases with a client-hostname set.
It isn't clear what behaviour one should see, but I would have expected leases where the domain is overridden for that interface, to be registered against that domain, rather than the default for the pfsense installation.
If the current behaviour is indeed undesirable, and the expected one I defined above is preferred, then I can see that this is not trivial to solve, as all leases appear to be put into a single file, and so it's impossible to tell which interface they came from (and whether a domain overried was set) without reading config from elsewhere.
Here's a previous mailing list conversation on the issue, which I was not involved in: [[http://lists.pfsense.org/pipermail/list/2013-February/003590.html]]
Updated by Steve Kerrison over 10 years ago
I should have added an example of how dhcpleases is invoked:
/usr/local/sbin/dhcpleases -l /var/dhcpd/var/db/dhcpd.leases -d example.org -p /var/run/dnsmasq.pid -h /var/etc/hosts
Where -d specifies the domain suffix to apply to all client-hostname entries that are found.
Updated by