latest v0.107.35 not resolve local dns names

[Just2Confuse]

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)

Custom (please mention in the description)

Installation

Other (please mention in the description)

Setup

On one machine

AdGuard Home version

v0.107.35

Action

My local AdGuard get an update today to v0.107.35. Since that time the local DNS resolve dosent work. I see only client IPs and not Names.

Im on DietPie (Raspi Zero 2W) and bevor this update everything looks fine

Expected result

DNS Names instead pure IP Adresses

Actual result

IP Adresses.

Additional information and/or screenshots

root@DietPi:~# uname -a
Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux
root@DietPi:~#
root@DietPi:~# /mnt/dietpi_userdata/adguardhome/AdGuardHome --version
AdGuard Home, version v0.107.35
root@DietPi:~#

[sleel]

Having the same problem

[TheCeet]

I guess eveyone has this issue now.
https://www.reddit.com/r/Adguard/comments/15as5az/adguard_home_is_unable_to_resolve_the_hostname_of/

My setup
Pi 4B, Diepi 64bit, Debian 12
Only issues after update to 0.107.35

[megakitsu]

Same here on Unraid, only since last update

[cenk]

Same on v0.108.0-a.633+5f8fa006

[EugeneOne1]

@Just2Confuse, hello and thanks for the report. We're actively investigating this, could you please help us providing some additional info? We'd like to check:

• Your verbose log, ideally with private resolving captured;
• A screenshot of your "Settings" → "DNS" → "Private reverse DNS servers section.

Since these may contain sensitive info, you may sent it to our devteam@adguard.com.

[Just2Confuse]

@EugeneOne1 Via Mail? This file wont grow. I also have Unbound, but if needed i can disable it. But it works till yesterday.

Update: Aftre a restart of my Zero 2 i get a better Debug-Output. Will send it via Mail.

[cenk]

OK. I sent the full verbose log via email. I am also having this problem. I hope the log will be useful.

[EugeneOne1]

@Just2Confuse, @cenk, we've received the logs. Looking through it we may conclude that AdGuard Home definitely ignores the data from local resolvers for some reason. Could you please perform the following command and share its output:

nslookup -debug <some-client-address> <resolver-address>

[Just2Confuse]

@Just2Confuse, @cenk, we've received the logs. Looking through it we may conclude that AdGuard Home definitely ignores the data from local resolvers for some reason. Could you please perform the following command and share its output:

nslookup -debug <some-client-address> <resolver-address>

Shure i can. My printer is not confindential :D ;)

root@DietPi:~# date
Thu Jul 27 13:30:46 BST 2023
root@DietPi:~# nslookup -debug 192.168.1.120 192.168.1.1
------------
    QUESTIONS:
        120.1.168.192.in-addr.arpa, type = PTR, class = IN
    ANSWERS:
    ->  120.1.168.192.in-addr.arpa
        name = EPSON4F2504Drucker.
        ttl = 0
    AUTHORITY RECORDS:
    ADDITIONAL RECORDS:
------------
120.1.168.192.in-addr.arpa      name = EPSON4F2504Drucker.

root@DietPi:~#

[cenk]

dietpi@ulasdietpi:~$ nslookup -debug 10.0.0.101 10.0.0.15
------------
    QUESTIONS:
        101.0.0.10.in-addr.arpa, type = PTR, class = IN
    ANSWERS:
    ->  101.0.0.10.in-addr.arpa
        name = ulas-j7prime.ulas.
        ttl = 0
    AUTHORITY RECORDS:
    ADDITIONAL RECORDS:
------------
101.0.0.10.in-addr.arpa name = ulas-j7prime.ulas.

[a904055262]

Same here on openwrt

[EugeneOne1]

@Just2Confuse, @cenk, I believe we've got it, we're going to push the fix to the edge channel later today.

[megakitsu]

Sorry late back, if you still need logs I will happily post mine however looks like you've got it! Thanks for looking into this so promptly and to everyone sending logs etc. 👍

[EugeneOne1]

@Just2Confuse, @cenk, @a904055262, @foxbludd, @sleel, @TheCeet, and everyone else concerned, we've pushed the edge release, could you please check if it fixes the issue? In short, we didn't take into account zero-TTL answers from upstream servers.

[cenk]

v0.108.0-a.634+300821a7 works perfect.

[Just2Confuse]

Im not sure what this edge means. On Dietpi its a little limited ^^

[TheCeet]

Im not sure what this edge means. On Dietpi its a little limited ^^

It's a pre-release build
Edge > alpha build
There are alse beta build.
and last: Production build (normal release)
See: https://github.com/AdguardTeam/AdGuardHome/blob/master/README.md#test-unstable-versions

[lutfor-diu]

having the same issue. in previous version worked fine.

[Siox0911]

Ok, this error chain will prevent me from doing further updates. Even updating to .34 was a huge mistake!

[EugeneOne1]

@Just2Confuse, hello again. Didn't TheCeet's comment help you install the edge build? I'd like to help you with that, but I don't have any information on how exactly have you installed the AdGuard Home.

[exoticprgmr]

I can confirm the issue after recent update to v0.107.35 via snap.

[EugeneOne1]

@exoticprgmr, as I mentioned, it seems we've fixed it in the latest edge, so could you please try it and check if it works there?

[exoticprgmr]

@exoticprgmr, as I mentioned, it seems we've fixed it in the latest edge, so could you please try it and check if it works there?

Thank you. Seems to be fixed on v0.108.0-a.635+79306cb4

[EugeneOne1]

@Just2Confuse, we're going to close this issue for now as several people have confirmed that it's fixed. We'll include the fix in the upcoming beta and production releases, but feel free to reopen the issue if the problem persists.