v0.107.43 doesn't respond to requests over port 53

[ossandcad]

Prerequisites

• [X] I have checked the Wiki and Discussions 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

• [X] 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, AMD64 (aka x86_64)

Installation

Snapcraft

Setup

On one machine

AdGuard Home version

v0.107.43

Action

dig +short @192.168.50.31 NS google.com - This works on v0.107.42, BUT not on v0.107.43. kdig -d @192.168.50.31 +tls-ca +tls-host=MYLOCALCN www.google.com - this works in both v0.107.42 and .43

Downgrading snap to .42 fixes the problem with no other changes.

Expected result

ns4.google.com. ns3.google.com. ns2.google.com. ns1.google.com.

Actual result

;; communications error to 192.168.50.31#53: timed out ;; communications error to 192.168.50.31#53: timed out ;; communications error to 192.168.50.31#53: timed out ;; no servers could be reached

Additional information and/or screenshots

No response

[udtcp]

for me it is working on v0.107.43

[blaine07]

for me it is working on v0.107.43

Is your instance Docker or in Ubuntu or etc?

[udtcp]

adguard home running on openwrt 23.05 on netgear r 7800

[ossandcad]

In my case:

1. Ubuntu 22.04.03 LTS
2. Installed via snap: Name Version Rev Tracking Publisher Notes adguard-home v0.107.42 6432 latest/stable ameshkov✓ - adguard-home v0.107.43 6448 latest/stable ameshkov✓ disabled
3. ufw status 443 ALLOW Anywhere 53 ALLOW Anywhere 53/tcp ALLOW Anywhere 853 ALLOW Anywhere
   53 (v6) ALLOW Anywhere (v6) 853 (v6) ALLOW Anywhere (v6)
   53/tcp (v6) ALLOW Anywhere (v6)

(apologies - missed this since email went to Promotions folder)

[knaggsy2000]

I've been getting some weird issues regarding resolving too, please check my post involving it - #6500

It might help, but can't promise anything,

[ghost]

Hi @ossandcad, thanks for the report.

I run AGH in the same environment on a RP3b+ and have not been able to reproduce this. Could you please update to the latest version of AGH and let me know how that goes for you?

[ossandcad]

Thanks @jslawler-gh - I should have clarified earlier - later versions definitely do not have this problem. Auto-updates via Snap and only had to blacklist that one version.