Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow queries overall when upstream to local domain should be returning NXDOMAIN but timeouts instead #6945

Closed
4 tasks done
felipejfc opened this issue Apr 28, 2024 · 1 comment

Comments

@felipejfc
Copy link

Prerequisites

Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

Installation

Docker

Setup

On one machine

AdGuard Home version

edge

Action

When I setup an upstream to my local domain:
[/local/]10.0.0.1 //which is an UDM PRO router
If some machine in the network is, for some reason, looking for names that don't exist, e.g. iPhone.local, adguard home will keep timing out when trying to resolve this name on upstream router, these requests build up and slow down everything else.
If I try to manually nslookup iPhone.local 10.0.0.1 from my PC, the upstream answers instantaneously with NXDOMAIN. I wonder why on adguard these requests are timing out instead.

Expected result

No slowlyness, when adguard home calls upstream to resolve a local domain that doesn't exist it should fail fast.

Actual result

Instead of failing fast I'm hitting timeouts as observed in the logs, e.g.:

2024/04/28 01:50:12.395395 [error] dnsproxy: upstream 10.0.0.1:53 failed to exchange ;aee03874-2f62-4298-9eb3-3a29536aa4bf.local.      IN       AAAA in 20.001546624s: exchanging with 10.0.0.1:53 over udp: read udp 10.0.0.51:39870->10.0.0.1:53: i/o timeout
2024/04/28 01:50:12.395381 [error] dnsproxy: 10.0.0.1:53: response received over udp: "exchanging with 10.0.0.1:53 over udp: read udp 10.0.0.51:36158->10.0.0.1:53: i/o timeout"
2024/04/28 01:50:12.395409 [error] dnsproxy: upstream 10.0.0.1:53 failed to exchange ;aee03874-2f62-4298-9eb3-3a29536aa4bf.local.      IN       A in 20.000735423s: exchanging with 10.0.0.1:53 over udp: read udp 10.0.0.51:41347->10.0.0.1:53: i/o timeout
2024/04/28 01:50:12.395410 [error] dnsproxy: 10.0.0.1:53: response received over udp: "exchanging with 10.0.0.1:53 over udp: read udp 10.0.0.51:38392->10.0.0.1:53: i/o timeout"
2024/04/28 01:50:12.395416 [error] dnsproxy: upstream 10.0.0.1:53 failed to exchange ;aee03874-2f62-4298-9eb3-3a29536aa4bf.local.      IN       AAAA in 20.001288487s: exchanging with 10.0.0.1:53 over udp: read udp 10.0.0.51:36158->10.0.0.1:53: i/o timeout
2024/04/28 01:50:12.395423 [error] dnsproxy: upstream 10.0.0.1:53 failed to exchange ;aee03874-2f62-4298-9eb3-3a29536aa4bf.local.      IN       A in 20.000679419s: exchanging with 10.0.0.1:53 over udp: read udp 10.0.0.51:38392->10.0.0.1:53: i/o timeout

Additional information and/or screenshots

On 10.0.0.1 is a UDM Pro router

@felipejfc
Copy link
Author

my bad. had a dns loop going on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant