Hi
I was reporting (https://forum.opnsense.org/index.php?topic=24931.0) this issue in 21.7 release. After some time it was fixed.
I did upgrade to 23.1 and and I'm seeing the problem again.
happen just now:
- new device connected to network
- new devices get IP and it can access local network and internet
- I can ping that new device from my laptop BUT only using IP
- if I am using hostname I get error saying not able resolve name ...
I did login to router and run this command:
sudo ps -aux|grep unbo
root 88022 5.1 3.3 197748 134948 - S Sun14 34:07.57 /usr/local/bin/python3 /usr/local/opnsense/scripts/unbound/logger.py (python3.9)
unbound 84539 0.0 1.4 145996 56208 - Ss Sun14 0:38.30 /usr/local/sbin/unbound -c /var/unbound/unbound.conf
root 87907 0.0 0.1 12756 2232 - Is Sun14 0:00.00 daemon: /usr/local/opnsense/scripts/unbound/logger.py[88022] (daemon)
jano 95697 0.0 0.1 12748 2364 0 S+ 18:45 0:00.01 grep unbo
then I did restart unbound in web gui and run that command on console again:
sudo ps -aux|grep unbo
root 76021 4.6 0.4 25764 15348 - Ss 18:45 0:05.32 /usr/local/bin/python3 /usr/local/opnsense/scripts/dhcp/unbound_watcher.py --domain doma (python3.9)
root 76350 1.5 2.8 192116 115176 - S 18:45 0:05.85 /usr/local/bin/python3 /usr/local/opnsense/scripts/unbound/logger.py (python3.9)
unbound 31762 0.0 1.3 145996 55064 - Ss 18:45 0:01.00 /usr/local/sbin/unbound -c /var/unbound/unbound.conf
root 76233 0.0 0.1 12756 2232 - Is 18:45 0:00.00 daemon: /usr/local/opnsense/scripts/unbound/logger.py[76350] (daemon)
jano 71423 0.0 0.1 12748 2364 0 S+ 18:46 0:00.01 grep unbo
As you can see after restarting unbound service watcher is running. But was not.
Just let me know which log to check (maybe I need to tune log level) to find out more details so I can help to find out what's going on.
Seeing the same on 23.7.8_1
After random period of time it is working again (DNS resolution).
Please find attached a host monitoring graph (last 35 days) of one access point that periodically is failing for a random time.
The AP was up and running fine all the time, but name resolution via unbound is not possible.
Since I set my dhcpd lease time < 86400 s this did not occur anymore.
???