Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Totoooool

#1
Thanks for your help @FullyBorked, i confirm that i've got exactly the same behaviour
- entry is present and valid in /var/dhcpd/var/db/dhcpd.leases
- no entry in /var/unbound/dhcpleases.conf

Even after dhcp/unbound restart, there aren't any errors in logs.
I've tried to reboot the whole device, but i've got the same behaviour, and no resolution !

But this morning, i've reboot again, and this time, i've got the resolution, something seems to be wrong since the last update of unbound  :(
#2
Hello Franco, thanks for your help,
i've checked this file, and I can see the presence of my lease, it's here
:-[
#3
Hello, since a recent upgrade (22.1.5 ~ 22.1.6) my unbound is unable to deserve the new devices which are added in DHCP leases, my option mark is well checked, but it's impossible to get anything from unbound. (i try to restart unbound/dhcp services, reboot opnsense, without any changes)
There arent any error/warn logs in unbound  :-\


If i try a command (ubuntu) like :

dig +search <hostname_in_dhcp_lease> @<OPNSENSE_IP>


i get

->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55137
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1


Do you have any advice to help me to debug/fix this issue ?
it worked before theses updates.