Adguard Home - Slow DNS response time

Hi, is there someone experiencing a very slow DNS response time on AdGuard Home 0.107.51 (update by @admon script) on Flint2 (firmware 4.6.2 - 28/Jun/2024 - Release Candiate)?

Wed Jul  3 15:31:08 2024 user.notice AdGuardHome[8758]: 2024/07/03 14:31:08.111142 [error] dnsproxy: quic://x-oisd.freedns.controld.com:853: response received over udp: "opening stream: failed to open a QUIC stream: timeout: no recent network activity"
Wed Jul  3 15:31:08 2024 user.notice AdGuardHome[8758]: 2024/07/03 14:31:08.152733 [error] dnsproxy: upstream quic://x-oisd.freedns.controld.com:853 failed to exchange ;logsink.devices.nest.com.	IN	 A in 41.645519ms: reading response from quic://x-oisd.freedns.controld.com:853: 0-RTT rejected
Wed Jul  3 15:35:56 2024 user.notice AdGuardHome[8758]: 2024/07/03 14:35:56.553402 [error] dnsproxy: quic://x-1hosts-lite.freedns.controld.com:853: response received over udp: "opening stream: failed to open a QUIC stream: timeout: no recent network activity"
Wed Jul  3 15:35:56 2024 user.notice AdGuardHome[8758]: 2024/07/03 14:35:56.575524 [error] dnsproxy: upstream quic://x-oisd.freedns.controld.com:853 failed to exchange ;graph.facebook.com.	IN	 A in 24.556558ms: reading response from quic://x-oisd.freedns.controld.com:853: 0-RTT rejected
Wed Jul  3 15:35:56 2024 user.notice AdGuardHome[8758]: 2024/07/03 14:35:56.595090 [error] dnsproxy: upstream quic://x-1hosts-lite.freedns.controld.com:853 failed to exchange ;ksn-ca-geo.kaspersky-labs.com.	IN	 A in 41.7072ms: reading response from quic://x-1hosts-lite.freedns.controld.com:853: 0-RTT rejected
Wed Jul  3 15:35:56 2024 user.notice AdGuardHome[8758]: 2024/07/03 14:35:56.886895 [error] dnsproxy: quic://x-hagezi-proplus.freedns.controld.com:853: response received over udp: "opening stream: failed to open a QUIC stream: timeout: no recent network activity"
Wed Jul  3 15:35:56 2024 user.notice AdGuardHome[8758]: 2024/07/03 14:35:56.908548 [error] dnsproxy: upstream quic://x-hagezi-proplus.freedns.controld.com:853 failed to exchange ;play.googleapis.com.	IN	 A in 21.715445ms: reading response from quic://x-hagezi-proplus.freedns.controld.com:853: 0-RTT rejected
Wed Jul  3 16:03:08 2024 user.notice AdGuardHome[8758]: 2024/07/03 15:03:08.648033 [error] dnsproxy: upstream quic://x-1hosts-lite.freedns.controld.com:853 failed to exchange ;epdg.epc.mnc010.mcc234.pub.3gppnetwork.org.	IN	 A in 20.903269ms: reading response from quic://x-1hosts-lite.freedns.controld.com:853: 0-RTT rejected
Wed Jul  3 17:34:47 2024 user.notice AdGuardHome[8758]: 2024/07/03 16:34:47.735846 [error] dnsproxy: upstream https://dns.quad9.net:443/dns-query failed to exchange ; IN	 SOA in 3.512403946s: expected status 200, got 502 from https://dns.quad9.net:443/dns-query

Probably that time the current network environment is busy, the response time of some DNS servers will be relatively slow. Is there a similar situation now?

Thanks, I restarted the statistics and now I can see all queries are under 100ms.
The average processing time is now 21ms.
So it seems ok.

1 Like