-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Adguard uses incorrect names #7532
Comments
Have you updated the DNS names for the devices on the router? |
Yes, I changed the names a long time ago. I didn't have Adguard on the PI back then. |
The rDNS Feature in AGH is broken since, i dont know...ever ? Now it works. |
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. |
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:
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.
The text was updated successfully, but these errors were encountered: