Timeout errors - Response recevied over udp

[renatoyamane]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question or ask for help

• I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, ARMv7

Installation

Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)

Setup

On a router, DHCP is handled by the router

AdGuard Home version

0.107.51

Action

After upgrading from 0.107.50 to 0.107.51 I started to see these errors below:

Fri Jun  7 08:43:20 2024 daemon.warn dnsmasq[4731]: nameserver 127.0.0.1 refused to do a recursive query
Fri Jun  7 09:14:21 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:14:21.508565 [error] dnsproxy: 127.0.0.1:53: response received over udp: "exchanging with 127.0.0.1:53 over udp: read udp 127.0.0.1:59025->127.0.0.1:53: i/o timeout"
Fri Jun  7 09:14:21 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:14:21.508706 [error] dnsproxy: upstream 127.0.0.1:53 failed to exchange ;150.6.168.192.in-addr.arpa.	IN	 SOA in 2.001038427s: exchanging with 127.0.0.1:53 over udp: read udp 127.0.0.1:59025->127.0.0.1:53: i/o timeout
Fri Jun  7 09:14:21 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:14:21.508565 [error] dnsproxy: 127.0.0.1:53: response received over udp: "exchanging with 127.0.0.1:53 over udp: read udp 127.0.0.1:56506->127.0.0.1:53: i/o timeout"
Fri Jun  7 09:14:21 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:14:21.508776 [error] dnsproxy: upstream 127.0.0.1:53 failed to exchange ;150.6.168.192.in-addr.arpa.	IN	 SOA in 2.001723775s: exchanging with 127.0.0.1:53 over udp: read udp 127.0.0.1:56506->127.0.0.1:53: i/o timeout
Fri Jun  7 09:14:24 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:14:24.433914 [error] dnsproxy: [::1]:53: response received over udp: "exchanging with [::1]:53 over udp: read udp [::1]:46063->[::1]:53: i/o timeout"
Fri Jun  7 09:14:24 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:14:24.434041 [error] dnsproxy: upstream [::1]:53 failed to exchange ;150.6.168.192.in-addr.arpa.	IN	 SOA in 2.001156477s: exchanging with [::1]:53 over udp: read udp [::1]:46063->[::1]:53: i/o timeout
Fri Jun  7 09:14:24 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:14:24.434826 [error] dnsproxy: [::1]:53: response received over udp: "exchanging with [::1]:53 over udp: read udp [::1]:42492->[::1]:53: i/o timeout"
Fri Jun  7 09:14:24 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:14:24.434916 [error] dnsproxy: upstream [::1]:53 failed to exchange ;150.6.168.192.in-addr.arpa.	IN	 SOA in 2.00137525s: exchanging with [::1]:53 over udp: read udp [::1]:42492->[::1]:53: i/o timeout
Fri Jun  7 09:15:51 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:15:51.106272 [error] dnsproxy: [::1]:53: response received over udp: "exchanging with [::1]:53 over udp: read udp [::1]:55499->[::1]:53: i/o timeout"
Fri Jun  7 09:15:51 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:15:51.106426 [error] dnsproxy: upstream [::1]:53 failed to exchange ;150.6.168.192.in-addr.arpa.	IN	 SOA in 2.000838985s: exchanging with [::1]:53 over udp: read udp [::1]:55499->[::1]:53: i/o timeout
Fri Jun  7 09:15:51 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:15:51.106272 [error] dnsproxy: 127.0.0.1:53: response received over udp: "exchanging with 127.0.0.1:53 over udp: read udp 127.0.0.1:44697->127.0.0.1:53: i/o timeout"
Fri Jun  7 09:15:51 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:15:51.106504 [error] dnsproxy: upstream 127.0.0.1:53 failed to exchange ;150.6.168.192.in-addr.arpa.	IN	 SOA in 2.001481132s: exchanging with 127.0.0.1:53 over udp: read udp 127.0.0.1:44697->127.0.0.1:53: i/o timeout
Fri Jun  7 09:15:53 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:15:53.255717 [error] dnsproxy: [::1]:53: response received over udp: "exchanging with [::1]:53 over udp: read udp [::1]:33618->[::1]:53: i/o timeout"
Fri Jun  7 09:15:53 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:15:53.255815 [error] dnsproxy: upstream [::1]:53 failed to exchange ;150.6.168.192.in-addr.arpa.	IN	 SOA in 2.001736635s: exchanging with [::1]:53 over udp: read udp [::1]:33618->[::1]:53: i/o timeout
Fri Jun  7 09:15:53 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:15:53.256082 [error] dnsproxy: 127.0.0.1:53: response received over udp: "exchanging with 127.0.0.1:53 over udp: read udp 127.0.0.1:49044->127.0.0.1:53: i/o timeout"
Fri Jun  7 09:15:53 2024 user.notice AdGuardHome[9325]: 2024/06/07 08:15:53.256130 [error] dnsproxy: upstream 127.0.0.1:53 failed to exchange ;150.6.168.192.in-addr.arpa.	IN	 SOA in 2.001394808s: exchanging with 127.0.0.1:53 over udp: read udp 127.0.0.1:49044->127.0.0.1:53: i/o timeout

Note also the IP address looks reversed:
What I see on the log: 150.6.168.192
What probably should be: 192.168.6.150

Upstream DNS servers (Load balancing mode):

https://dns.quad9.net/dns-query
https://doh.opendns.com/dns-query
https://security.cloudflare-dns.com/dns-query
tls://security.cloudflare-dns.com
quic://dns.adguard-dns.com
quic://zero.dns0.eu
https://dns.adguard-dns.com/dns-query
tls://dns.adguard-dns.com
h3://cloudflare-dns.com/dns-query
# Cisco OpenDNS:
sdns://AQAAAAAAAAAADjIwOC42Ny4yMjAuMjIwILc1EUAgbyJdPivYItf9aR6hwzzI1maNDL4Ev6vKQ_t5GzIuZG5zY3J5cHQtY2VydC5vcGVuZG5zLmNvbQ
# Quad9:
sdns://AQMAAAAAAAAADDkuOS45Ljk6ODQ0MyBnyEe4yHWM0SAkVUO-dWdG3zTfHYTAC4xHA2jfgh2GPhkyLmRuc2NyeXB0LWNlcnQucXVhZDkubmV0
# AdGuard:
sdns://AgMAAAAAAAAADDk0LjE0MC4xNC4xNCCaOjT3J965vKUQA9nOnDn48n3ZxSQpAcK6saROY1oCGQw5NC4xNDAuMTQuMTQKL2Rucy1xdWVyeQ
# Comodo Secure DNS:
sdns://AQAAAAAAAAAACjguMjAuMjQ3LjIg0sJUqpYcHsoXmZb1X7yAHwg2xyN5q1J-zaiGG-Dgs7AoMi5kbnNjcnlwdC1jZXJ0LnNoaWVsZC0yLmRuc2J5Y29tb2RvLmNvbQ
quic://x-hagezi-proplus.freedns.controld.com
quic://x-1hosts-lite.freedns.controld.com

Bootstrap DNS servers:

208.67.222.222
1.1.1.1
208.67.220.220
9.9.9.9
8.8.8.8
149.112.112.10
94.140.15.15
2a10:50c0::ad1:ff
94.140.14.14
2a10:50c0::ad2:ff
[2a10:50c0::ad1:ff]:5443
2001:4860:4860:0:0:0:0:6464
76.76.2.42
45.90.28.128

Bug 6897 is still happening on this version

Expected result

No erros

Actual result

Erros reported above

Additional information and/or screenshots

No response

[diegoweb]

I'm having the exact same problem if I have Unbound as my Upstream DNS.
Watchtower container updated my ADH and after that, everything stopped working. So I'm not sure what version it was previously.

This issue started yesterday. I've tried to roll back 1 version but it didn't help.
I'm having to use a public dns server in "Upstream DNS Server" in order to have ADH to work.

[Cebeerre]

Hi @renatoyamane

The IPs don't look reversed, this is how PTR records (reverse DNS lookups) are declared. If you look at the log, you'll notice that the timeout is actually coming from 127.0.0.1:53 which I assume you've declared in the "Private reverse DNS servers" section.

The thing is that something is quering for the SOA registry, which I guess is not implemented in the DNS Server that you're using as private reverse resolver ending with a timout of the query.

Pushing SOA requests to the upstream private resolvers whas added in v0.107.49 so this entries have probably been showing up in the log since that release.

[Cebeerre]

I'm having the exact same problem if I have Unbound as my Upstream DNS. Watchtower container updated my ADH and after that, everything stopped working. So I'm not sure what version it was previously.

This issue started yesterday. I've tried to roll back 1 version but it didn't help. I'm having to use a public dns server in "Upstream DNS Server" in order to have ADH to work.

Your issue sounds like a completely different thing. If you're starting unbound as a container as well, you might be having conectivity issues between the two containers. Check how you configured the networks if you're using the internal docker DNS resolver to declare Unbound in the AGH config.

[renatoyamane]

Hi @renatoyamane

The IPs don't look reversed, this is how PTR records (reverse DNS lookups) are declared. If you look at the log, you'll notice that the timeout is actually coming from 127.0.0.1:53 which I assume you've declared in the "Private reverse DNS servers" section.

The thing is that something is quering for the SOA registry, which I guess is not implemented in the DNS Server that you're using as private reverse resolver ending with a timout of the query.

Pushing SOA requests to the upstream private resolvers whas added in v0.107.49 so this entries have probably been showing up in the log since that release.

Thanks.
My settings are:

So, should I change the empty box (Private reverse DNS servers) to the IP of the router where AdGuard is installed (like: 192.168.1.1)?