blocking "local" - why? #2901
Unanswered
hutchwilco
asked this question in
Q&A
Replies: 3 comments 3 replies
-
Probably, you should ask Dan Pollock about it, I don't understand why blocking it either |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hello, |
Beta Was this translation helpful? Give feedback.
0 replies
-
@hutchwilco @MilesTEG1 Filter maintainers decisions and use cases sometimes may not fit for every users but you don't need to bother them. In this case, you can create a custom filtering rule to whitelist "local". as mentioned, it's enough to create one rule. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
AdGuard Home is operating with a handful of "standard" blocklists including Dan Pollock's List.
I have a lot of blocked requests that are simply labelled "local". I've no idea why you'd block this, or indeed why my various machines on my home network are simply making a DNS request for "local". It seems to happening often - several times a second. One machine is a server of sorts - Plex, Sonarr, Radarr etc, which all talk to each other so I'd expect them to be using local.
Is Ad Guard Home nevertheless seeing this query, even though it's resolved within the network routing on the server itself?
Can anyone tell me why you'd bother blocking this?
![Screen Shot 2021-04-01 at 11 16 16 PM](https://user-images.githubusercontent.com/4792731/113280703-23efaf80-9341-11eb-9e38-e38013206070.png)
Beta Was this translation helpful? Give feedback.
All reactions