Pi Hole dashboard shows ads blocked but I see no difference

Help
1

Expected Behavior:

I have a Verizon router (ARC-XCI55AX) and it restricts what can be done to the DNS so I am using it as my internet access and as a pass through to my TP-Link which I am using for home router and for the raspberry pi. I hope I am saying that correctly. I did set the static IP for the r-pi on the tp-link. I am very new to this whole thing but learning. All my devices go to tp-link.

The Pi Hole dashboard indicates that ads are being blocked.

I do have a ROKU that I use for all my TV streaming services.

Actual Behavior:

Every streaming service still has all the ads as before. Including Netflix, Pluto, Peacock, etc.

Shouldn't I notice a difference?

I have no idea what a debug token is or how to run it.

Sorry, major newbie here.

Thanks

2

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

sudo pihole -d
3

here is the token: https://tricorder.pi-hole.net/H2IX3DJy/

4

It depends on the service and in general you should accept the fact that the ads shown in such services can not be blocked by Pi-Hole sadly because they can not be blocked on DNS level :slight_smile:

Sometimes you can do something about it by intercepting DNS traffic to External DNS Servers via the Firewall of your Router and the right DNAT/SNAT Rules but even that does not always help!

The general opinion about those devices seems to be that they are pure spyware/adware and blocking their privacy exploiting functions is a serious challenge/issue !! :frowning:

5

Your debug log shows the router is advertising 2 DNS servers - Pi-hole and itself:

    dns-server: 192.168.0.231
    dns-server: 192.168.0.1
    router: 192.168.0.1

As a consequence, all devices will receive this information and them each operating system will decide how to use these servers. Most operating systems try both servers. Some decide to use one, then the other. There is no way to predict which one will be actually used.

When a device uses the router as DNS server, Pi-hole is bypassed.

Solution:
(if possible) force your router to advertise only Pi-hole IP.

Make sure there is no checkbox saying to "include the router's IP as DNS server", or something similar.

Try settings Pi-hole IP as both server 1 and server 2 on the router.
If the router interface doesn't allow to use the same IP twice, try to add 0.0.0.0 as the other DNS server.