New DHCP Static Mappings not resolving in DNS (unbound)
motonuke last edited by
This feature has worked in the past for me.
Here is the scenario: I create a static mapping in DHCP and give it a hostname. Once that is created, I am able to resolve this new hostname via NSLOOKUP, etc. However, sometime in the last few weeks/months, this has stopped working. Any NEW static DHCP mapping that I add will not resolve (whether showing online or offline). Old entries that used to work, still do.
Another bit of data: if a new device comes on the network and DHCP is able to get it's hostname (it's gets populated in the DHCP leases table), then I am able to resolve this name. I am not adding any static entries anywhere in this scenario.
Tertiary data: In the DHCP logs, devices that work will show their names in the DHCPREQUEST and DHCPACK log entries, devices that do not work will not show any names.
Jul 2 16:53:00 dhcpd DHCPACK on 192.168.1.359 to 00:00:00:00:00:00 (Jessica-PC) via bge1
Jul 2 16:43:42 dhcpd DHCPACK on 192.168.1.340 to 00:00:00:00:00:00 via bge1
Manual entries into the DNS Resolver Host overrides table, of course, work as intended.
This was happening on 2.3.3 and I just migrated to 2.4.3_p1 (newer hardware). I did bring over my config, and this issue has come along for the ride.
I will also add these peculiar log entries:
Jul 2 16:35:29 dhcpleases kqueue error: unkown Jul 2 16:35:29 dhcpleases Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process.
Searching around doesn't reveal this exact issue and some of the troubleshooting steps didn't really show anything.
Appreciate any guidance., I don't want to go nuclear on this thing, it's setup just perfectly.