Unbound dns & adguard home shows me these errors

Troubleshooting
1

My updated unbound shows me this error. is it normal or something special for my machine

root@wyse:/etc/unbound/unbound.conf.d# sudo journalctl --full --no-pager --lines 30 -u unbound.service
Aug 27 10:46:15 wyse systemd[1]: Starting unbound.service - Unbound DNS server...
Aug 27 10:46:15 wyse (unbound)[622]: unbound.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_OPTS
Aug 27 10:46:15 wyse unbound[622]: [622:0] info: start of service (unbound 1.22.0).
Aug 27 10:46:15 wyse systemd[1]: Started unbound.service - Unbound DNS server.

on other side adguard home shows me these error

root@wyse:/etc/unbound/unbound.conf.d# sudo journalctl --full --no-pager --lines 30 -u adguardhome.service
Aug 29 16:01:34 wyse AdGuardHome[574]: 2025/08/29 16:01:34.773542 [error] dnsproxy: exchange failed upstream=127.0.0.1:5335 question=";wpad.emea.tsp.ad.\tIN\t A" duration=20.003501637s err="exchanging with 127.0.0.1:5335 over udp: read udp 127.0.0.1:39555->127.0.0.1:5335: i/o timeout"
Aug 29 16:29:11 wyse AdGuardHome[574]: 2025/08/29 16:29:11.821862 [error] dnsproxy: unpacking udp packet err="dns: buffer size too small"
Aug 29 16:29:14 wyse AdGuardHome[574]: 2025/08/29 16:29:14.821242 [error] dnsproxy: unpacking udp packet err="dns: buffer size too small"
Aug 29 16:33:05 wyse AdGuardHome[574]: 2025/08/29 16:33:05.374468 [error] dnsproxy: unpacking udp packet err="dns: buffer size too small"
2

I would very thank full to some expert who help to fine tune the unbound/adguardhome on dietpi optimization. unbound & adguard home showing error in UDP connection with default deitpi configuration. in some places it is written to increase memory size like

sysctl -w net.core.rmem_default=7864320
sysctl -w net.core.rmem_max=26214400
sysctl -w net.core.wmem_default=7864320
sysctl -w net.core.wmem_max=26214400

to change this they are asking for edit file /etc/sysctl.conf but in dietpi trixie this file does not exist. so some thing is change while we upgrade from bookworm to trixie.

3

On Debian, /etc/sysctl.conf is a legacy single file, but the more modern approach is to place configuration snippets inside /etc/sysctl.d/*.conf, which makes it easier to manage custom and package-provided settings.

This has nothing to do with DietPi. There isn’t even a DietPi Trixie. It’s Debian Trixie. DietPi is just a collection of Bash scripts. DietPi itself supports multiple versions of Debian (Bookworm, Trixie, and already Forky).

4

thanks, any recommendation for memory sizes and any other finetuning you suggest for this bundle project?

5

I don’t use AGH and don’t have experience with it.