Display which blocklist is responsible for a block

Feature Requests Duplicate
1

It would be useful to know which blocklist is responsible per blocked query. For instance, if I find myself going through a lot of trouble whitelisting things, I can imagine that if they were all blocked due to a single list, I may want to consider disabling that list entirely. But I don't know that I have a way to easily identify that right now by looking at blocked queries. If they just displayed the list(s) they exist on inline, that could be very useful in identifying impact of various list inclusion.
Thanks.

Jeremy

2

Please consider searching existing Feature Requests before posting a new one, e.g. Shows which blocklist the domain name is blocked from.

2 Likes
3

Multiple blocklists could carry the domain that is blocked. If Pi-hole were to search the individual blocklists for each query that is blocked, this would significantly hamper performance.

The ability exists to search blocklists for any domain that is blocked, via two methods.

  1. From the web GUI > Tools > Query lists

  2. From the command line (this method offers a bit more flexibility with options):

pihole -q -adlist -exact domainnamehere

Example of the command line output:

pihole -q -adlist -exact flurry.com
 Exact matches for flurry.com found in:
   http://sysctl.org/cameleon/hosts
   https://gitlab.com/quidsup/notrack-blocklists/raw/master/notrack-blocklist.txt
   https://hosts-file.net/emd.txt
   https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts;showintro=0
   https://raw.githubusercontent.com/anudeepND/blacklist/master/adservers.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_malvertising.txt
   https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
   https://v.firebog.net/hosts/AdguardDNS.txt
   https://v.firebog.net/hosts/Prigent-Ads.txt
4

I don't think it has to happen in realtime before the DNS response is delivered, per the performance concern. In fact, it only really would need to happen when the blocked queries were viewed. If performance were still an issue even with that, then it could be an option as to whether to display it or not.
I also realize that multiple blocklists could carry the same domain- in such an instance, the expectation would be that all lists blocking a given domain would be listed beside it.

Thanks for the suggestions, but my aim here with this feature was to make this information readily accessible, so it becomes apparent without a lot of manual effort each time for the type of reasoning I described.

6

Closed to existing feature request here: