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
But this is blocking i.e www.landsend.de in my case, too.
Additionaly AdGuard Home is not responding at all to the query: DIG connection timeout!
It took me a while to figure this out because the verbose log said the domain is in the block list. And the check filter tool said it's not. 2024/01/03 11:24:48.603433 3224#8621 [debug] access: request A www.landsend.de is in access blocklist
Even the custom rule "@@||www.landsend.de^$important" does not override the behavior.
Hope this helps the development team.
Happy new year to everybody and keep up the great work! Thanks
The text was updated successfully, but these errors were encountered:
MichaelS75
changed the title
"*.lan" filter in DNS-Settings->Disallowed domains blocking lookups for FQDN beginning with www.lan* and throws a dig connection timeout
"*.lan" filter in DNS-Settings->Disallowed domains blocking lookups for FQDN beginning with www.lan* and causing a dig connection timeout
Jan 3, 2024
But in this case the "check filter tool" should take it into account by saying i.e "Blocked by DNS Settings".
That might reduce confusion and one can find errors in the filter rules much faster...
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
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
v0.107.43
Action
dig "www.landsend.de" A
Expected result
Actual result
Additional information and/or screenshots
I use the default filter rules for local domains in DNS-Settings -> Disallowed domains (german: Nicht zugelassene Domains) with the following config:
But this is blocking i.e www.landsend.de in my case, too.
Additionaly AdGuard Home is not responding at all to the query: DIG connection timeout!
It took me a while to figure this out because the verbose log said the domain is in the block list. And the check filter tool said it's not.
2024/01/03 11:24:48.603433 3224#8621 [debug] access: request A www.landsend.de is in access blocklist
Even the custom rule "@@||www.landsend.de^$important" does not override the behavior.
Hope this helps the development team.
Happy new year to everybody and keep up the great work! Thanks
The text was updated successfully, but these errors were encountered: