Adguard uses incorrect names

[Mister-XY]

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)

Linux, ARMv7

Installation

Other (please mention in the description)

Setup

On one machine

AdGuard Home version

0.107.55

Action

Replace the following command with the one you're calling or a
description of the failing action:

 nslookup 192.168.178.19
19.178.168.192.in-addr.arpa     name = Thomas-Smartphone-Xiaomi.fritz.box.
19.178.168.192.in-addr.arpa     name = Xiaomi-11-Lite-5G-NE.fritz.box.

Expected result

I want see the correct Names how it set like Fritzbox Router

Actual result

I see the old names or what they were called before the Fritzbox was renamed.

Additional information and/or screenshots

For a long time now, I've noticed that all the clients in Adguard Home are named incorrectly. This means that they often get the name they had before they were renamed.
Of course, you could store all the names in /etc/host with the corresponding IP, but this solution is not very well thought out. If I change the IP in the router, then it also has to be changed manually in /etc/host. This means that you are basically always forced to do something else. This problem does not exist in Pihole.

[Dynamic5912]

Have you updated the DNS names for the devices on the router?

[Mister-XY]

Yes, I changed the names a long time ago. I didn't have Adguard on the PI back then.

[whyisthisbroken]

The rDNS Feature in AGH is broken since, i dont know...ever ?
I tried also with my and got no luck, so i added all names in the hosts file. (/etc/hosts)

Now it works.

[Mister-XY]

I think the names were correct 1-2 years ago and after an update from Adguard they were no longer correct and are displayed as they are now. I'm ruling out the /etc/host thing because the name changes when the IP changes.
Suppose I enter the name "Hummel" for 192.168.178.9
and for some reason I have to assign the IP 192.168.178.9 differently in the router, then the name for the IP is no longer correct.
That means I would have to remember to change the /etc/host as well.

[saint-lascivious]

The rDNS Feature in AGH is broken since, i dont know...ever ?

I'm just chiming in here to say that rDNS works fine here for local domain discovery (I have some magic to map out my local domain in unbound with local-data/local-data-ptr config).

My first question would be asking whether or not PTR records for your local domain actually exist/are provided by anything in your network, and my second question would be if yes is AGH actually configured to direct reverse lookups for private ranges to said destination?

[whyisthisbroken]

Can you share your magic with me you created in Unbound? I've tried it before, but it's not working properly
Or maybe post your AGH settings if it works for you?

[saint-lascivious]

Can you share your magic with me you created in Unbound?

Sure.

Well. Kind of. I can't really share the magic to generate the config for a given host as that's all very proprietary to my local network and high availability stuff, I can share an example of the resulting config covering a range of common values (A, AAAA, TXT and PTR), additionally demonstrating two slightly different ways of handling PTR records with either traditional local-data or local-data-ptr shorthand.

The example uses an FQDN (sub.domain.tld), but it could just as easily be a domain or hostname supplied instead.

Note that this configuration is found under the server: configuration header.

server:
    # sub.domain.tld
    local-zone: "sub.domain.tld." static
    local-data: "sub.domain.tld. 3600 IN A 192.168.1.10"
    local-data: "sub.domain.tld. 3600 IN AAAA fd80::aaaa:bbbb:cccc:1234"
    local-data: "sub.domain.tld. 3600 IN AAAA fe80::aaaa:bbbb:cccc:1234"
    local-data: "sub.domain.tld. 3600 IN AAAA 2404:4404::aaaa:bbbb:cccc:1234"
    local-data: 'sub.domain.tld. 3600 TXT "sub.domain.tld"'
    local-data: "10.1.168.192.in-addr.arpa. 10800 IN PTR sub.domain.tld."
    local-data-ptr: "fd80::aaaa:bbbb:cccc:1234 3600 sub.domain.tld"
    local-data-ptr: "fe80::aaaa:bbbb:cccc:1234 3600 sub.domain.tld"
    local-data-ptr: "2404:4404::aaaa:bbbb:cccc:1234 3600 sub.domain.tld"