Pihole Adblocking not working properly

[Jonas_Kruger]

Expected Behaviour:

Blocking of domains listed in the standard adlist on my main pc
My Hardware (PiHole):

• Rasperry Pi 4 with 4Gb Ram
• OS : Raspian GNU 11
• IPv4: 192.168.178.90
  -- listed as only DNS Server in router settings

(My Desktop Pc):

• Ryzen 5 3600 with 32 Gb Ram
• B450 Mainboard
• OS: Windows 10 22H2

Actual Behaviour:

• domains found in adlist are not being blocked (ex. flurry.com)
• test website shows all ads : Pi-Hole Ad Tester – Fuzz The Pi Guy

Output from ipconfig /all :
Verbindungsspezifisches DNS-Suffix: fritz.box
Beschreibung. . . . . . . . . . . . . . : TP-Link Wireless PCI Express Adapter
Physische Adresse . . . . . . . . .: D0-37-45-C7-05-2E
DHCP aktiviert. . . . . . . . . .. . . : Ja
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::464b:131c:45d4:db37%17(Bevorzugt)
IPv4-Adresse . . . . . . . . . . . . . . : 192.168.178.37(Bevorzugt)
Subnetzmaske . . . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . . . . .: Samstag, 25. März 2023 13:55:52
Lease läuft ab. . . . . . . . . . . . . . : Dienstag, 4. April 2023 14:00:59
Standardgateway . . . . . . . . . . . : 192.168.178.1
DHCP-Server . . . . . . . . . . . . . . : 192.168.178.1
DHCPv6-IAID . . . . . . . . . . . . . . : 282081093
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-27-AE-4E-C2-2C-F0-5D-81-0C-BC
DNS-Server . . . . . . . . . . . . . . . : 192.168.178.90
NetBIOS über TCP/IP . . . . . . . . : Aktiviert

Pihole Version:
Pi-hole version is v5.16.1 (Latest: v5.16.1)
AdminLTE version is v5.19 (Latest: v5.19)
FTL version is v5.22 (Latest: v5.22)

Debug Token:

https://tricorder.pi-hole.net/oS1HkEaP/

[chrislph]

@Jonas_Kruger

domains found in adlist are not being blocked (ex. flurry.com)

Are they appearing in the Query Log?

What do you get from each the following commands?

nslookup pi.hole

nslookup flurry.com

nslookup flurry.com 192.168.178.90

[Bucking_Horn]

Also note that above commands should be run from a client, not from the machine hosting Pi-hole.

[Jonas_Kruger]

Output of nslookup pi.hole
Server: pi.hole
Address: 192.168.178.90

Name: pi.hole
Addresses: fe80::505b:5508:d84e:4b68
192.168.178.90

Output of nslookup flurry.com
Server: pi.hole
Address: 192.168.178.90

Nicht autorisierende Antwort:
Name: flurry.com
Addresses: 212.82.100.150
74.6.136.150
98.136.103.23

Output of nslookup flurry.com 192.168.178.90
Server: pi.hole
Address: 192.168.178.90

Nicht autorisierende Antwort:
Name: flurry.com
Addresses: 74.6.136.150
98.136.103.23
212.82.100.150

Commands were executed on my home pc (not hosting the pihole service)

Domains are appearing in the query log (which should show being blocked, but it still doesn't work)

[jfb]

@Jonas_Kruger

Commands were executed on my home pc

Is this the PC that is assigned to management group 2 in Pi-hole? There is no blocking assigned to that group (or any group other than the default group), so Pi-hole is effectively disabled for all clients in those groups.

*** [ DIAGNOSING ]: Domainlist (0/1 = exact white-/blacklist, 2/3 = regex white-/blacklist)
   id     type  enabled  group_ids     domain                                                                                                date_added           date_modified        comment                                           
   -----  ----  -------  ------------  ----------------------------------------------------------------------------------------------------  -------------------  -------------------  --------------------------------------------------
   1       1          1  0             rr4---sn-4g5e6nsr.googlevideo.com                                                                     2022-09-25 19:43:39  2022-09-25 19:43:39  Added from Query Log                              
   2       1          1  0             m.2020mustang.com                                                                                     2022-09-26 21:19:34  2022-09-26 21:19:34  Added from Query Log                              
   4       1          1  0             ads.pubmatic.com                                                                                      2023-03-25 12:52:15  2023-03-25 12:52:15  Added from Query Log                              
   5       1          1  0             ads.everesttech.net                                                                                   2023-03-25 12:52:51  2023-03-25 12:52:51  Added from Query Log                              
   7       1          1  0             adventori.com                                                                                         2023-03-25 12:55:42  2023-03-25 12:55:42  Added from Query Log                              
   8       1          1  0             px.ads.linkedin.com                                                                                   2023-03-25 12:55:49  2023-03-25 12:55:49  Added from Query Log                              
   9       1          1  0             adservice.google.com                                                                                  2023-03-25 12:57:10  2023-03-25 12:57:10  Added from Query Log                              
   10      1          1  0             ads.avads.net                                                                                         2023-03-25 13:00:31  2023-03-25 13:00:31  Added from Query Log                              
   11      1          1  0             connect-metrics-collector.s-onetag.com                                                                2023-03-25 13:47:28  2023-03-25 13:47:28  Added from Query Log                              
   12      1          1  0             gaa.adscale.de                                                                                        2023-03-25 13:47:43  2023-03-25 13:47:43  Added from Query Log                              
   13      1          1  0             cs.adingo.jp                                                                                          2023-03-25 13:48:02  2023-03-25 13:48:02  Added from Query Log                              


*** [ DIAGNOSING ]: Adlists
   id     enabled  group_ids     address                                                                                               date_added           date_modified        comment                                           
   -----  -------  ------------  ----------------------------------------------------------------------------------------------------  -------------------  -------------------  --------------------------------------------------
   1            1  0             https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts                                      2022-09-25 19:23:15  2023-03-25 14:16:59  Migrated from /etc/pihole/adlists.list

[Jonas_Kruger]

I have corrected the ad list group assignment. Now it seems to be working.
Thank you all for helping me with my own incompetence.