Skip to content
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

AdguardHome DNS caching old value from /etc/hosts #7512

Open
4 tasks done
kesavananbu opened this issue Dec 17, 2024 · 1 comment
Open
4 tasks done

AdguardHome DNS caching old value from /etc/hosts #7512

kesavananbu opened this issue Dec 17, 2024 · 1 comment

Comments

@kesavananbu
Copy link

kesavananbu commented Dec 17, 2024

Prerequisites

Platform (OS and CPU architecture)

Linux, ARMv7

Installation

Docker

Setup

On one machine

AdGuard Home version

v0.107.55

Action

Before restarting the adguard docker, /etc/hosts have entry for
172.23.0.5 plex

After restarting the container, i have updated the entry in /etc/hosts
172.23.0.11 plex

If I execute the nslookup or enter the plex in the browser the ip it resolved to 172.23.0.5 instead of 172.23.0.11.
So basically it caching and not refreshing the entries for dynamic data.

If I restart the container, it loads the latest data /etc/hosts available. So need a fix for this to consider the dynamic host entry in /etc/hosts file.

nslookup plex 192.168.1.2

Expected result

Server: 192.168.1.2
Address: 192.168.1.2#53

Non-authoritative answer:
Name: plex
Address: 172.23.0.11

Actual result

Server: 192.168.1.2
Address: 192.168.1.2#53

Non-authoritative answer:
Name: plex
Address: 172.23.0.5

Additional information and/or screenshots

upload_issue

@kesavananbu
Copy link
Author

kesavananbu commented Dec 17, 2024

Similar issue #6711
@EugeneOne1
Let me know if I'm missing something here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant