Unbound DNS Log Errors

[roblang]

I have recently set-up a fresh install of OPNSense and everything is working apart from the Unbound DNS log containing a lot of errors (see sample below).

2024-11-29T19:53:44   Error   unbound   [49173:2] error: recvfrom 45 failed: Protocol not available   
2024-11-29T19:53:44   Error   unbound   [49173:2] error: recvfrom 46 failed: Protocol not available   
2024-11-29T19:53:44   Error   unbound   [49173:2] error: recvfrom 45 failed: Protocol not available   
2024-11-29T19:53:44   Error   unbound   [49173:2] error: recvfrom 46 failed: Protocol not available   
2024-11-29T19:53:44   Error   unbound   [49173:2] error: recvfrom 45 failed: Protocol not available   
2024-11-29T19:53:44   Error   unbound   [49173:2] error: recvfrom 46 failed: Protocol not available   
2024-11-29T19:53:38   Error   unbound   [49173:0] error: recvfrom 35 failed: Protocol not available   
2024-11-29T19:53:37   Error   unbound   [49173:2] error: recvfrom 48 failed: Protocol not available   
2024-11-29T19:53:37   Error   unbound   [49173:3] error: recvfrom 36 failed: Protocol not available   
2024-11-29T19:53:36   Error   unbound   [49173:2] error: recvfrom 39 failed: Protocol not available

Can someone point me in the right direction to troubleshoot where these are being generated.

Thanks in advance.

[roblang]

I have just upgraded to latest version of OpnSense and still getting these log messages.  Does anyone have any idea where to start troubleshooting?

[newsense]

Start troubleshooting by describing your Unbound setup. Clearly you changed something there.

[roblang]

I have had the same error since initial installation (24.7).  Log files were getting flooded with errors so I switched to DNSMasq.  Now need wildcard hostname resolution so turned Unbound back on, all default settings apart from "Register ISC DHCP4 Leases" and "Register DHCP Static Mappings".  OPNSense is now on (25.1.2) but the errors are the same as when on (24.7) with unbound enabled.

[newsense]

Last time this recvfrom issue came up on the forum was in 2023 and was fixed in 23.1.1_2 apparently by this commit

https://github.com/opnsense/core/commit/7ebe361

Unsure why this issue resurfaces again after 2 years, your best bet would be to open a ticket on Github opnsense/core referencing this thread.