You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
only upstream DNS servers currently on list resolve dominas
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
The text was updated successfully, but these errors were encountered:
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
Found out the issue - two devices had hidden upstreams very easy to miss can close the case (dont know how)
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)
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
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
The text was updated successfully, but these errors were encountered: