Anyone who runs a Roku and has a Pi-hole on their network:
I came across some good regex blocking for it. Let me know if you want it, and I'll toss it in a paste as it can't be posted here.
@voltronic I just deployed my first pi-hole earlier today. No roku though.
@john_b
Welcome to the team. What are you using for resolvers?
@voltronic so far I'm sticking with the same Google upstream resolvers that I was using previously. I'll experiment with others in the coming weeks, I'm sure - just wanted to limit the variables a bit for the initial setup.
@voltronic I meant to add that I'm definitely open to suggestions/recommendations if you've got any. I do use a number of Google services and I've seen that some of those (I'm looking at you, Stadia) seem to work more reliably when using Google DNS.
@john_b
I used to use Quad 9 (9.9.9.9). There's Cloudflare (1.1.1.1).
If you have a pi-hole though, I really recommend you use dnscrypt-proxy, or what I use now, unbound. Unbound is a bit easier to set up, and then you are hosting your own resolver. It's in the guide in my pinned toots.
@john_b
I have seen that first thread, but not the second one. Lots of great tips in there I didn't think of, from someone who clearly knows much more Linux than I do. (That covers the vast majority of Linux users!)
I will be implementing some of these things on my setup. Thanks!
@voltronic Ok, implemented. Thanks again for (1) inspiring me and (2) pointing me in the right direction to get started.
I also used some tips from this reddit thread to tune things a bit:
https://www.reddit.com/r/pihole/comments/d9j1z6/unbound_as_recursive_dns_server_slow_performance/
And this one had a good suggestion for automating root.hints updates:
https://www.reddit.com/r/pihole/comments/dezyvy/into_the_pihole_you_should_go_8_months_later/
And my wife hasn't complained about things breaking (did I mention I was doing this remotely? *evil cackle*) so it must have worked! 👨🔧