Not enough ads blocked

Expected Behaviour:

Expecting to have much more than 5% ads blocked while using a lot of lists :

  • Raspberry Pi OS 64bits
  • Raspberry Pi 4
  • Using dnscrypt-proxy

Actual Behaviour:

I'm currently having around 5% Ads blocked, a few months ago it was much much more with less ad lists, but I had to change ISP provider and my Sd Card for my RPI, so I did a fresh install and disabled DHCP from the provider's router and activated DHCP from Pi-hole, I also set the static IP's as it should, but I still get a lot of ads.

nslookup xp.apple.com
Server:         127.0.2.1
Address:        127.0.2.1#53

Non-authoritative answer:
xp.apple.com    canonical name = xp.itunes-apple.com.akadns.net.
xp.itunes-apple.com.akadns.net  canonical name = xp.apple.com.edgekey.net.
xp.apple.com.edgekey.net        canonical name = e17437.dsct.akamaiedge.net.
Name:   e17437.dsct.akamaiedge.net
Address: 92.122.148.85
Name:   e17437.dsct.akamaiedge.net
Address: 2a02:26f0:b200:192::441d
Name:   e17437.dsct.akamaiedge.net
Address: 2a02:26f0:b200:1bf::441d
Name:   e17437.dsct.akamaiedge.net
Address: 2a02:26f0:b200:199::441d
tail -f /var/log/dnscrypt-proxy/query.log
[2023-03-20 11:15:49]   127.0.0.1       assets.raspberrypi.com  HTTPS   PASS    174ms   dct-de1
[2023-03-20 11:15:49]   127.0.0.1       staging-assets.raspberrypi.com  HTTPS   PASS    188ms   scaleway-fr
[2023-03-20 11:19:46]   127.0.0.1       mabbox.bytel.fr HTTPS   PASS    0ms     -
[2023-03-20 11:20:20]   127.0.0.1       api-mifit-de2.zepp.com  A       PASS    0ms     -
[2023-03-20 11:20:26]   127.0.0.1       3.3.d.2.7.2.e.f.f.f.0.2.d.8.e.3.0.0.f.9.6.c.8.3.1.6.8.0.1.0.0.2.ip6.arpa        PTR     NXDOMAIN        1250ms  dct-nl1
[2023-03-20 11:20:27]   127.0.0.1       6.5.6.a.d.9.8.9.2.9.3.0.6.b.5.e.0.0.f.9.6.c.8.3.1.6.8.0.1.0.0.2.ip6.arpa        PTR     NXDOMAIN        1743ms  ams-doh-nl
[2023-03-20 11:20:35]   127.0.0.1       e.6.a.c.4.a.e.f.f.f.c.8.f.c.6.0.0.0.f.9.6.c.8.3.1.6.8.0.1.0.0.2.ip6.arpa        PTR     NXDOMAIN        1048ms  dct-ru1
[2023-03-20 11:20:52]   127.0.0.1       mabbox.bytel.fr HTTPS   PASS    0ms     -
[2023-03-20 11:21:28]   127.0.0.1       xp.apple.com    A       PASS    19ms    adguard-dns-unfiltered
[2023-03-20 11:21:28]   127.0.0.1       e17437.dsct.akamaiedge.net      AAAA    PASS    19ms    ams-dnscrypt-nl

Debug Token:

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

The 5% percentage doesn't mean "only 5% of all ads were blocked and 95% of ads are shown".

The percentage means: only 5% of all DNS requests were blocked by Pi-hole and the rest was not considered ads.

Blocking percentages can be expected to fluctuate over time.
By themselves, they wouldn't be a reliable indication.

Did the number of DNS requests also drop significantly?

Together, that could suggest that DNS requests may be going elsewhere, by-passing Pi-hole.

Your debug log shows your Pi-hole host device to have full IPv6 connectivity.
Perhaps your router is advertising an non-Pi-hole IPv6 address as DNS server?

It seems that my ISP box doesn't forward everything to Pi-hole ... I'm trying to understand why and how I can fix that.

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