What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

DNS Resolution Not Working

Zim

Regular Contributor
Running into a bizarre issue since updating AGH to the latest version, v0.107.57 about a week ago. I have tried resetting the router, installing and uninstalling different scripts, in different order. In another thread, someone mentioned adding 127.0.0.1 and ::1 under "Allowed clients" list under "Access settings" in AGH. But no luck.

I'm running AGH + Unbound. When I run Unbound alone everything appears to be working fine, when I installed AGH the DNS queries stop going through OR are severely delayed. In AGH I see response times of 1,400+ms from 127.0.0.1:53535. Running netstat -nlp | grep :53 I do see AGH listening on port 53 and I see Unbound listening on 127.0.0.1:53535.

The upstream server in AGH is correctly set to:
127.0.0.1:53535
tcp://127.0.0.1:53535

Another thing I've noticed (since the AGH update) is when AGH + Unbound is running, Unbound stats for "Number of queries dropped because request list was full" is very high. About 60+% of the queries are being dropped. Without AGH the same number drops to less than 0.3%. I'm running AXE16000 so CPU and memory is not the issue.

Not sure what the issue is or to start to fix this.
 
What scripts are you talking about?
The usual suspects:
  • AdGuard Home
  • Unbound
  • scMerlin
  • Scribe
  • vnStat
I've spent a good portion of the week trying to reset, reflash, reconfigure the router from scratch, but the problem persists. I've now gotten to a point where the DNS queries stop sporadically. I looked into the logs when the DNS stops and this is what I see.

Code:
Mar  7 17:05:20 AdGuardHome[12269]: 2025/03/07 17:05:20.173731 [error] dnsproxy: unpacking udp packet err="dns: buffer size too small"
Mar  7 17:05:23 AdGuardHome[12269]: 2025/03/07 17:05:23.137805 [error] dnsproxy: unpacking udp packet err="dns: buffer size too small"

Poking around the forum, found a thread with the similar issue. Suggestion was to disable "Disable resolving of IPv6 addresses" in AGH. Made sure of it, but the DNS still stops resolving sporadically. Further digging in the system logs, I'm noticing a LOT of these messages at the time the DNS stops working.

Code:
AdGuardHome[12269]: ERROR response received addr=tcp://127.0.0.1:53535 proto=tcp status="exchanging with tcp://127.0.0.1:53535 over tcp: read tcp 127.0.0.1:49122->127.0.0.1:53535: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=127.0.0.1:53535 proto=udp status="exchanging with 127.0.0.1:53535 over udp: read udp 127.0.0.1:39849->127.0.0.1:53535: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=tcp://127.0.0.1:53535 proto=tcp status="exchanging with tcp://127.0.0.1:53535 over tcp: read tcp 127.0.0.1:49124->127.0.0.1:53535: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=127.0.0.1:53535 proto=udp status="exchanging with 127.0.0.1:53535 over udp: read udp 127.0.0.1:52156->127.0.0.1:53535: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=127.0.0.1:53535 proto=udp status="exchanging with 127.0.0.1:53535 over udp: read udp 127.0.0.1:46915->127.0.0.1:53535: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=tcp://127.0.0.1:53535 proto=tcp status="exchanging with tcp://127.0.0.1:53535 over tcp: read tcp 127.0.0.1:49128->127.0.0.1:53535: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=tcp://8.8.8.8:53 proto=tcp status="dialing 8.8.8.8:53 over tcp: dial tcp 8.8.8.8:53: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=tcp://8.8.8.8:53 proto=tcp status="dialing 8.8.8.8:53 over tcp: dial tcp 8.8.8.8:53: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=tcp://9.9.9.9:53 proto=tcp status="dialing 9.9.9.9:53 over tcp: dial tcp 9.9.9.9:53: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=tcp://9.9.9.9:53 proto=tcp status="dialing 9.9.9.9:53 over tcp: dial tcp 9.9.9.9:53: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=tcp://9.9.9.9:53 proto=tcp status="dialing 9.9.9.9:53 over tcp: dial tcp 9.9.9.9:53: i/o timeout"
AdGuardHome[12269]: ERROR response received addr=tcp://8.8.8.8:53 proto=tcp status="dialing 8.8.8.8:53 over tcp: dial tcp 8.8.8.8:53: i/o timeout"
.
.
.
.
.
.
hostapd: wl3.2: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
hostapd: wl3.2: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
hostapd: wl3.2: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated
hostapd: wl3.2: STA xx:xx:xx:xx:xx:xx RADIUS: starting accounting session X45C0B52789C123
hostapd: wl3.2: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)

Then everything starts working again. I reboot the router just for good measure, but after some time the problem happens again and the cycle continues. This only started happening after upgrading AGH to v0.107.57

I've just uninstalled AGH, so far (2 hours) things have been running fine!
 
Last edited:

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Back
Top