AdguardTeam / AdguardTeam/AdGuardHome

Timeouts over UDP

Open
#6,668 2 comments 0 reactions 0 assignees View on GitHub
docker waiting for data
Dominant language
TypeScript
Stars
36.9k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Description

### Prerequisites

- [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer

- [X] I have searched other issues and found no duplicates

- [X] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)

- [X] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)

### Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

### Installation

Docker

### Setup

On one machine

### AdGuard Home version

v0.107.43

### Action

For some time now, I struggle with slow internet. I finally found time to look into the problem and found out that I often get timeouts when resolving over UDP. Interestingly, there are no timeouts when resolving over TCP (`nslookup -vc ...`) .

```sh
~> nslookup www.gmail.com
;; communications error to 192.168.2.50#53: timed out
Server: 192.168.2.50
Address: 192.168.2.50#53

Non-authoritative answer:
Name: www.gmail.com
Address: 216.58.215.229
Name: www.gmail.com
Address: 2607:f8b0:400f:807::2005
```

Interesting as well: On the server itself (where the docker image is running), there are no timeouts with `nslookup www.gmail.com localhost` but with `nslookup www.gmail.com 192.168.2.50`.

I am back now on `v0.107.29` and everything is working again. I can't tell if this is the last version without this problem. I currently don't have the time for more trial and error... 😀

### Expected result

No timeouts when resolving over UDP (see above).

### Actual result

Timeouts when resolving over UDP (see above).

### Additional information and/or screenshots

Used port mapping: `-p 53:53/tcp -p 53:53/udp`

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.