Interesting. I’m using nextdns on my router, I had manually blocked ads.roku.com and now have the Stephen Black block list enabled too but I’m still getting ads.
Now that I look through my nextdns logs, I don’t see my roku at all so something seems to be up with my config. Thanks for the help!
Something to be aware of, some devices will straight ignore your DNS settings in DHCP if they can’t get to their ads. My iPhone 13 did that. I had to block port 53 udp/tcp for everything but the piholes.
I’m sure eventually we’re going to see DNS over https doing the same and I’m 100% ready to mitm all devices that pull that bullshit…
It came free with one of the standardized block lists. Let me go see what my pi hole is blocking.
I can’t tell exactly what it’s nixing without rebooting it and there’s somebody watching it right now.
Here are the obvious candidates from the Stephen Black block list
P.ads.roku.com
Austin.logs.roku.com
Mobile.logs.roku.com
Scribe.logs.roku.com
logs.Roku.com
Interesting. I’m using nextdns on my router, I had manually blocked ads.roku.com and now have the Stephen Black block list enabled too but I’m still getting ads.
Now that I look through my nextdns logs, I don’t see my roku at all so something seems to be up with my config. Thanks for the help!
If you can’t get it straightened out Hit me up again here and I’ll restart my Roku and see if I can figure out what else it’s hitting
Thanks! I’ve just got it working now - something weird is going on with my ddns setup but manually linking my IP to the nextdns profile did it.
Something to be aware of, some devices will straight ignore your DNS settings in DHCP if they can’t get to their ads. My iPhone 13 did that. I had to block port 53 udp/tcp for everything but the piholes.
I’m sure eventually we’re going to see DNS over https doing the same and I’m 100% ready to mitm all devices that pull that bullshit…