YouTube plays ads on my nVidia Shield, like Pi-Hole never existed

Please follow the below template, it will help us to help you!

Expected Behaviour:

[Ads should not play within YouTube on my nVidia Shield. I'm wondering if my shield is bypassing pi-hole? I've set the dhcp to static and pointed only DNS1 to my PI-address.. The DNS2 I left blank, as instructed.]

Actual Behaviour:

[Ads are playing]

Debug Token:

[r32q9q20m6]

Any logging from this device in pihole?
If not, this shield may be using preconfigured dns.
I have seen some users that change the shield to fixed ip en pihole dns

Yeah I posted a token. But how do I know if its using preconfigured dns? I did set it tu manually go to my pihole address.

The token links to your uploaded debug log. Typically the debug log won't show this.

Tail your pihole.log (pihole -t or from the Admin GUI (tools > tail pihole.log). While you are viewing the log, use the nVidia to start, stop and load YouTube videos. If you don't see any activity in the pihole.log from that client, it is using another source for DNS.

Ahh I see. Thanks I'll check as soon as I'm home and report

I made a firewall rule on my EdgeRouter to force all dns trafic to my pi hole

Is that the option 1? I couldn't find out how to do it on my Asus router

Yes, too bad my fritzbox does not allow me to do this.
Only thing I could do was create ip routes for some dns ip's

But blocking ads on youtube seems to be getting more and more difficult.
First thing Keem must do is verify the shield is using the pi as dns.

1 Like

you need uBlock Origin extension in your browser because blocking on DNS level is not enough.

1 Like

That will work for a browser, but the OP is having problems with a separate device that isn't serving content through a browser.

1 Like

Hi guys. I checked now, it seems that it's working.. the .128 is my nVidia Shield IP that i statically set. See attached screen

OK. Now that Pi-Hole is seeing the nVidia box, you might still get some ads on various platforms (YouTube is one).

Pi-Hole is a domain blocker, and typically ads have been served from separate domains than the content. By identifying and blocking the ad-serving domains, you can block the ads. Your subscribed blocklists are lists of ad-serving (or malware or phishing, etc) domains.

What YouTube and others are starting to do is serve the ads from the same domain as the content, but using a rotating subdomain. Pi-Hole can't block the ad domains without also blocking the content. It's a never ending cat and mouse game.

Note that even if you are unable to block the YouTube ads completely, your Pi-Hole is still blocking a lot of other content (tracking, ads, etc.) for other domains (Neflix, etc) on the nVidia.

Here are some related threads (long in the first case). I recommend reading them all for some insight.

https://www.reddit.com/r/pihole/comments/8hetls/a_question_and_my_youtube_and_spotify_blocklists/

Ahh I understand! I also found some lists to try to block out as much as possible. Thanks for your detailed feedback. At least now I know that the pihole works.

Should I use blocklist or blacklist when finding .txt lists?

I don't understand this question. Please clarify.

For example I found this: pi-hole/hosts at master · hulkhaugen/pi-hole · GitHub

Some guides says I should paste the whole link in to blocklist under "settings". But I also see a "blacklist" above settings.. So there's a blocklist and a blacklist.. Not sure which one to use..

Also, is there an easy way to catch the ads-addresses? For example opening YouTube on my computer and have an extension of some sort that will catch all the ads addresses for me to go through afterwards?

Blocklist or blacklist.. Which one of them should I use? I need to have a little more detailed description than that msatter. Also, I don't use ublock since I am running a shield.. But I am looking for a way to snap up all the ads addresses.

To clarify the terminology:

  1. Block lists are publicly maintained lists of domains, hosted on a web location somewhere. When you subscribe to a "block list", Pi-Hole will go to the web and read the entire contents of that block list and add it to gravity (the master list of blocked domains). If you look in your block lists (Web admin GUI > Settings > Blocklists), you see that it consists of web addresses that lead to block lists maintained at each web site.

I would avoid a lot of the lists you find sprinkled around the internet. Many have been adapted from other ad blocker software (AdBlock, for example) and don't follow the correct format. The best collection of blocklists in my opinion is maintained at: https://firebog.net by wally3k, one of the developers.

  1. The black list is a locally maintained (on your Pi-Hole) list of domains that you want blocked, typically put here because they aren't on one of your subscribed block lists.

  2. White list is a black list in reverse. It's local, but you are telling Pi-Hole not to block that domain.

My advice - start with the seven standard block lists that you installed with Pi-Hole. See how that works for you. If you are seeing things you don't want, then blacklist them. If things are blocked that you want, white list them.

There is a big temptation to go out and collect block lists like treasure coins. Typically all this will do is give you a lot of false blocks and drive you nuts.

DNSThingy is a Chrome browser extension that works well to show you all the domains that are requested with a website. It is discussed a bit in this thread, which is worth a read:

2 Likes

OK. Do not have a nvidia shield, In this device: is it possible to use a proxy?..
If not, blocking the ads will be possible only on DNS level (pihole)
If you can set a proxy, there is options.

I use privoxy and inject the adblock pro rules (easylist) in there.
msatter is promoting ublock, but you can not use ublock on your nvidia shield, unless there is some way of installing plugins on that nvidia shield.

Regarding the blacklists: here is what I am using:

https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
http://sysctl.org/cameleon/hosts
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
http://www.squidblacklist.org/downloads/dg-ads.acl
https://smokingwheels.github.io/Pi-hole/allhosts
http://www.malwaredomainlist.com/hostslist/hosts.txt
http://osint.bambenekconsulting.com/feeds/c2-dommasterlist.txt
http://malc0de.com/bl/ZONES
https://isc.sans.edu/feeds/suspiciousdomains_High.txt
http://osint.bambenekconsulting.com/feeds/dga-feed-high.csv
https://hosts-file.net/grm.txt
https://reddestdream.github.io/Projects/MinimalHosts/etc/MinimalHostsBlocker/minimalhosts
https://raw.githubusercontent.com/StevenBlack/hosts/master/data/KADhosts/hosts
https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.Spam/hosts
https://v.firebog.net/hosts/static/w3kbl.txt
https://adaway.org/hosts.txt
https://v.firebog.net/hosts/AdguardDNS.txt
https://raw.githubusercontent.com/anudeepND/blacklist/master/adservers.txt
https://v.firebog.net/hosts/Easylist.txt
https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts;showintro=0
https://raw.githubusercontent.com/StevenBlack/hosts/master/data/UncheckyAds/hosts
https://v.firebog.net/hosts/Easyprivacy.txt
https://v.firebog.net/hosts/Prigent-Ads.txt
https://raw.githubusercontent.com/quidsup/notrack/master/trackers.txt
https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.2o7Net/hosts
https://raw.githubusercontent.com/crazy-max/WindowsSpyBlocker/master/data/hosts/spy.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_malvertising.txt
https://hosts-file.net/exp.txt
https://hosts-file.net/emd.txt
https://hosts-file.net/psh.txt
https://mirror.cedia.org.ec/malwaredomains/immortal_domains.txt
https://www.malwaredomainlist.com/hostslist/hosts.txt
https://bitbucket.org/ethanr/dns-blacklists/raw/8575c9f96e5b4a1308f2f12394abd86d0927a4a0/bad_lists/Mandiant_APT1_Report_Appendix_D.txt
https://v.firebog.net/hosts/Prigent-Malware.txt
https://v.firebog.net/hosts/Prigent-Phishing.txt
https://raw.githubusercontent.com/quidsup/notrack/master/malicious-sites.txt
https://ransomwaretracker.abuse.ch/downloads/CW_C2_DOMBL.txt
https://ransomwaretracker.abuse.ch/downloads/LY_C2_DOMBL.txt
https://ransomwaretracker.abuse.ch/downloads/TC_C2_DOMBL.txt
https://ransomwaretracker.abuse.ch/downloads/TL_C2_DOMBL.txt
https://v.firebog.net/hosts/Shalla-mal.txt
https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.Risk/hosts
https://raw.githubusercontent.com/uBlockOrigin/uAssets/master/filters/annoyances.txt
https://raw.githubusercontent.com/uBlockOrigin/uAssets/master/filters/badware.txt
https://raw.githubusercontent.com/uBlockOrigin/uAssets/master/filters/experimental.txt
https://raw.githubusercontent.com/uBlockOrigin/uAssets/master/filters/filters.txt
https://raw.githubusercontent.com/uBlockOrigin/uAssets/master/filters/privacy.txt
https://raw.githubusercontent.com/uBlockOrigin/uAssets/master/filters/resource-abuse.txt
https://raw.githubusercontent.com/uBlockOrigin/uAssets/master/filters/resources.txt
https://raw.githubusercontent.com/uBlockOrigin/uAssets/master/filters/unbreak.txt
https://raw.githubusercontent.com/EnkoNeko/pie/master/PiHole/Adlists/GoogleAds.txt

Jeroen

1 Like

Nice, thanks! Will add them.. And yes, I have a proxy setting on the nvidia shield. Is there an wasy way of doing what you're saying?