DNS Timeouts while using Unbound

[Vuurmuur]

I'm using unbound as an intermediate cache which is advertised through DHCP. But I'm getting DNS timeouts while using Unbound:

Code Select Expand


>nslookup google.com

Server:  opnsense.xxxxxxxx.xxx
Address:  xxx.xxx.xxx.xxx (opnsense box address)

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
Non-authoritative answer:
Name:    google.com
Addresses:  2a00:1450:400e:808::200e
          172.217.20.78


When I query 1.1.1.1 directly I'm receiving a quick response:

Code Select Expand


>nslookup google.com 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    google.com
Addresses:  2a00:1450:400e:808::200e
          172.217.20.78


I already have 'Forwarding Mode' enabled, changing this does not yield different results.
I have tried disabling Suricata but this does not have any impact.
Successive requests still result in DNS timeouts, the result should be cached on first query if I'm not mistaken.

Any suggestions on why this is happening and how to fix it?

Versions
OPNsense 20.7.1-amd64
FreeBSD 12.1-RELEASE-p8-HBSD
LibreSSL 3.0.2

Performance
Processor: Intel(R) Celeron(R) J4005 CPU @ 2.00GHz (2 cores)
Memory: 22 % ( 1752/7961 MB )
Load averages: 0.38, 0.23, 0.18

[Vuurmuur]

Apparently I had one of the options for hardware offloading still enabled.
This didn't cause issues before 20.7 but disabling all hardware offloading fixed the issues.