"
I ran across this thread with very similar experience to the OP. I migrated from pfSense using the same hardware and same configuration (manually reconfigured) and found DNS to be terribly slow despite unbound stats not showing an obvious culprit.
Under System > Log Files > Backend (/ui/diagnostics/log/core/configd) I did notice a couple dozen of this peculiar message:
I couldn't put my finger on what it was, but it does seem that once I changed IPv6 configuration on the WAN interface to "None" rather than the default DHCP (my ISP doesn't offer IPv6) and disabled it on the LAN interface as well, unbound restarted and things have been smooth since and I don't see that message any longer.
I'll update the thread if I learn more.
For prosperity here are some details of my setup:
Under System > Log Files > Backend (/ui/diagnostics/log/core/configd) I did notice a couple dozen of this peculiar message:
Code Select
2022-09-22T12:06:41-07:00 Error configd.py Timeout (120) executing : unbound stats I couldn't put my finger on what it was, but it does seem that once I changed IPv6 configuration on the WAN interface to "None" rather than the default DHCP (my ISP doesn't offer IPv6) and disabled it on the LAN interface as well, unbound restarted and things have been smooth since and I don't see that message any longer.
I'll update the thread if I learn more.
For prosperity here are some details of my setup:
Code Select
Versions:
OPNsense 22.7.4-amd64
FreeBSD 13.1-RELEASE-p2
OpenSSL 1.1.1q 5 Jul 2022
CPU type:
Intel(R) Celeron(R) CPU J3160 @ 1.60GHz (4 cores, 4 threads)
