Blacklist exact domain doesn't seem to be working

Help
1

Expected Behaviour:

Blacklisted domains (atconnect.npo.nl and atconnect-npo-nl-cddc.at-o.net). Expected to get a "unable to resolve dns" from my webbrowser when surfing to atconnect.npo.nl.
Running my pihole on:

  • RPI 2B (processor armv71)
    versions
  • core: v5.1.2
  • web: v5.1.1
  • FTL: v5.2
  • lighttpd: 1.4.53
  • php: 7.3.19
  • os: raspbian v10
  • IPv4 (disabled v6 in router dhcp)

Actual Behaviour:

Blacklisted domain(s) are exact domains, even when entered from query log it doesn't seem to be blocking the domain atconnect.npo.nl. When surfing via a webbrowser the 1 pixel is still loaded and it appears in the query log as ok or even cached. Tried to re-enter the domains to the blacklist, manually and via query log. Restarted the dns resolver, restarted the whole system and flushed the logs. After doing each of these steps, i've also flushed the dns cach on my client (ipconfig /flushdns). And when i'm pinging the domain. It seems to get timouts. but when using a webrouwser (edge, chorme) it is still loaded and appears in the query log.

Debug Token:

debug token: https://tricorder.pi-hole.net/fniyjdmr20!blacklist not working|690x413

2

It would seem you've added atconnect.npo.nl to both your whitelists and blacklists:

*** [ DIAGNOSING ]: Domainlist (0/1 = exact white-/blacklist, 2/3 = regex white-/blacklist)
   id    type  enabled  group_ids     domain             date_added           date_modified        comment                                           
   ----  ----  -------  ------------  -----------------  -------------------  -------------------  ---------------------
   75    0           1  0             atconnect.npo.nl   2020-09-23 17:57:26  2020-09-23 17:57:26  Added from Query Log 
   86     1          1  0             atconnect.npo.nl   2020-09-24 09:11:15  2020-09-24 09:11:15  Added from Query Log

See also Pi-hole 5 release notes for blocking precedence.

3

What the... i don't remember doing that on purpose. probably happend accedently when, apparently double clicking or so, when i was administrating the query log on my phone via the webclient. thank you for noticing. i've been crunching my brain on this. it solved it right away!

4

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.