DHCP lease hostname not always registering with DNS Resolver

[dopey]

I'm using the dns resolver (unbound) and not the dns forwarder running on 2.2.4 and notice that it seems like at some point, the dhcp hostname is not registering for the dns resolver.

I did some digging and people have reported this problem but none of the solutions work.

I'm fairly certain everything is properly configured.
DNS Resolver has Register DHCP leases in the DNS Resolver checked.

the dhcpleases process:

root    70720  0.0  0.0  12408  2208  -  Is    5:59AM    0:00.59 /usr/local/sbin/dhcpleases -l /var/dhcpd/var/db/dhcpd.leases -d internal.moonteeth.com -p /var/run/unbound.pid -u /var/unbound/dhcpleases_entries.conf -h /var/etc/hosts

is running.

looking at /var/dhcpd/var/db/dhcpd.leases shows the the dhcp lease entries correctly with a client-hostname correct.

If i reboot pfsense/restart the unbound, it seems to pick up the exisitng dhcpleases, but it's not picking them up dynamically.

I see nothing in the system log that seems to be relevant although i occasionally see this:
Aug 22 05:31:21 host dhcpleases: kqueue error: unkown

One of the forum posts I found on this topic surmised that the dhcpleases failed to parse the file correctly becuase of a bad character but that seems unlikely given a restart of the system allows it to parse the leases.  But still, I'm not sure how to troubleshoot that.

I found the source to dhcpleases on github and didn't see any obvious verbose mode to figure out what's going on.

Thoughts on how to debug this?

[doktornotor]

Known bug, look at Redmine. https://redmine.pfsense.org/issues/4931

[dopey]

Thanks.  That definitely looks like the problem.

[q54e3w]

i was just wrangling with this exact issue - looks like it was just resolved in redline a week ago so expect we'll see it fixed in the next release. Thanks guys.