_It should block ads including in-app ads:
-hardware: raspberry pi 3b
Actual Behaviour:
_It doesn't block ads in-app ads and site ads as before. I had it set up for awhile and it had been working well until a couple months ago I suddenly saw ads in some apps. I tried restart the pi, flushed the DNS but nothing helped so I did a clean install but it still has the same issue. I suspect that it has something to do with Ipv6 but I'm not sure?
I don't think neither msn.com nor furry.com should be blocked in any list (in terms of ads). The domain to be checked is flurry.com, which should result 0.0.0.0 because it exists in many lists to be blocked.
Run from inside your Pi-hole host machine, the following command would list all IP addresses associated with a given network interface, in this case for eth0:
ip -6 address show eth0
The interface name should match the one that your Pi-hole is aware of, as displayed in some of the options under Interface settings at Settings | DNS in PI-hole's UI.
There will be quite a few of them.
Avoid public GUA addresses (range 2000::/3) - they are likely to change regularly, and Pi-hole has to be reachable via a stable IP.
Note that if your router supports it, I would prefer to disable propagating an IPv6 DNS resolver altogether.
That is correct and worth checking (even though Pi-hole supplies the necessary DNS replies for canary domains for FireFox).
But it has no impact on Yuqiriin's issue of a router advertising its own IPv6 address as local DNS resolver. That has to be addressed separately in one of the ways I've listed above.
after reaching out to my internet provider, I was informed that I could not do anything to the ipv6, so I was about to give up on using pi-hole. Fortunately, I reset my router and now it start working like before!
That may only be temporary - if your router continues to advertise Comcast's DNS server's IPv6 address, then clients will by-pass Pi-hole.
You want to re-verify which DNS servers your clients are using, e.g. by running an nslookup and scrutinising the actual Server: in use, or by running ipconfig /all from a Windows client and checking its DNS server section for Comcast's IPv6 addresses.
