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

n/r can close this #6967

Closed
4 tasks done
candybars2021 opened this issue May 5, 2024 · 1 comment
Closed
4 tasks done

n/r can close this #6967

candybars2021 opened this issue May 5, 2024 · 1 comment

Comments

@candybars2021
Copy link

candybars2021 commented May 5, 2024

Found out the issue - two devices had hidden upstreams very easy to miss can close the case (dont know how)

Prerequisites

Platform (OS and CPU architecture)

OpenBSD, AMD64 (aka x86_64)

Installation

GitHub releases or script from README

Setup

On a router, DHCP is handled by the router

AdGuard Home version

v0.107.48

Action

Query log and stats repeatedly shows resolution (not via cache) of domains based on secure upstream DNS servers long removed (DNS flushed, devices rebooted etc, many times).

Also local domains such as [/secure/lan/]192.168.30.1 ignore rule and "lan.lan" or "secure.secure" attempts to resolve upstream, while not allowed there. Local server above responds to other requests
``

Expected result

  1. only upstream DNS servers currently on list resolve dominas
  2. excpetiopns for local domains handled locally as above.

Actual result

I explained, Note also very recent (less than 1hr statistics ) was reset many times. In this example upstream DNS set to 103.86.96.100 and 103.86.99.100 ONLY (except local domains) and secure cloudflare and cloud 9 active as if they were ghosts.

Additional information and/or screenshots

Screenshot 2024-05-05 at 2 59 05 Screenshot 2024-05-05 at 3 00 24 Screenshot 2024-05-05 at 3 00 57 Screenshot 2024-05-05 at 3 01 08
@candybars2021 candybars2021 changed the title AdGuard Home continees to use upstream DNS servers that were long removed from the upstream list and cache was flushed , and ignoring local domain resolution exceptions n/r can close this May 5, 2024
@candybars2021
Copy link
Author

can clouds

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