Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pi-hole v6

pi-hole.net

Post reply on HN
Print view View original

91–100 of 316 posts

Re: Pi-hole v6

#91

Post by wkyleg »

In my experience Pi hole is a very worthwhile investment. People who used my internet when I had one would remark how much faster it was. Everything in general seems faster, even things that you wouldn't think of. I typically use Brave for browsing which has good ad blocking capabilities, but this adds a whole additional layer.

The only reason I don't use one now is that I travel a lot more so it's irrelevant, and I have to work enough on tools with Google/Vercel/other analytics that it is just very inconvenient.

Regarding smart TVs, I have found that it's better to just use an Apple TV or Kodi box and never connect to them internet though. Having said, I gave my TV away because I never used it, so this might not be as up to date. A Pi hole will block ads on smart TVs though.

Re: Pi-hole v6

#94

Post by nothrabannosir »

xrisk wrote: post #83
BHSPitMonkey wrote: post #44

Earlier quoted context omitted.

Is a DNS blackhole the right way to restrict your TV from doing bad things? The software running on the device might not even use DNS lookups to connect to hosts as it pleases. Your router is probably the better place to add guardrails.

It’s a start for sure, a TV that’s really out to track you might well be able to circumvent these blocks, but most TVs (and indeed most tracking technologies on the web) to my understanding are not so sophisticated. For the average person who wants to enjoy some of the smart features of their TV this is a good compromise. And I’m not sure what you mean by the router being the better place to add guardrails. What sort…

Smart TV opt-out telemetry is malicious.

Re: Pi-hole v6

#95

Post by paxys »

MyOutfitIsVague wrote: post #38
andy_xor_andrew wrote: post #21

I set up pi-hole recently after hearing about it for years. I was kind of surprised at a lack of really basic features (imo): There isn't any kind of "dry run" or "phantom" mode, where requests are not actually blocked, but appear marked in the log UI as "would be blocked". This is super important because I want to see all the things my home network is doing that would be blocked before I actually hit the big red but…

> It's also not possible (or not clear) how to have different behavior for different clients There's a menu item for that: Clients. You create a group, add a client to that group, and configure blocking for that group. To have what you want, you create a group that has just one client in it.

It's slightly more complicated. What you are suggesting works if (1) you are using Pi-hole as a DHCP server or (2) all your devices are individually configured to use the Pi-hole IP address for DNS resolution. What's more likely though is that you just point your router's DNS setting to Pi-hole, and in that case there is only one client on the Pi-hole dashboard - your router.

Re: Pi-hole v6

#96

Post by zufallsheld »

uncharted9 wrote: post #53
zufallsheld wrote: post #25

Earlier quoted context omitted.

However you can't use it on the phone while not at home (aside from using vpn/wireguard), but nextdns allows it. As for the latency - is it really noticeable?

my biggest gripe with NextDNS is not having an ability to add custom blocklists. I'd gladly pay for it even if there was a paid tier with this feature.

It seems you can add domains to the deny list via their api: https://nextdns.github.io/api/#profiles

So atleast there's that.

Re: Pi-hole v6

#97

Post by _chris_ »

wkyleg wrote: post #91

In my experience Pi hole is a very worthwhile investment. People who used my internet when I had one would remark how much faster it was. Everything in general seems faster, even things that you wouldn't think of. I typically use Brave for browsing which has good ad blocking capabilities, but this adds a whole additional layer. The only reason I don't use one now is that I travel a lot more so it's irrelevant, and I…

Wouldn’t a smart tv do something ... smarter than just using the default dns given to it by the network?

I’m not up to speed on this stuff but I thought pihole only blocked the simplest stuff from devices that play nice?

Re: Pi-hole v6

#98

Post by xrisk »

nothrabannosir wrote: post #94
xrisk wrote: post #83

Earlier quoted context omitted.

It’s a start for sure, a TV that’s really out to track you might well be able to circumvent these blocks, but most TVs (and indeed most tracking technologies on the web) to my understanding are not so sophisticated. For the average person who wants to enjoy some of the smart features of their TV this is a good compromise. And I’m not sure what you mean by the router being the better place to add guardrails. What sort…

Smart TV opt-out telemetry is malicious.

Edited to clarify what I mean.

Re: Pi-hole v6

#99

Post by newman314 »

unsnap_biceps wrote: post #4

Does anyone know if pihole is ever going to add DoH or similar support natively? I've had such troubles with cloudflared awhile back that I gave up on DoH, but would love to encrypt those queries.

You can insert dnscrypt-proxy inline between PiHole and an upstream server. So it'll work something like the following:

Client --DNS--> pinhole --DNS--> dnscrypt-proxy (localhost) --DoH--> upstream

Not the prettiest but it works.

Re: Pi-hole v6

#100

Post by mrmuagi »

laweijfmvo wrote: post #55
LeoPanthera wrote: post #7

I've been using AdGuard Home, which does pretty much the same thing, but is slightly better polished, with things like support for DoH and OSs other than Linux. https://github.com/AdguardTeam/AdGuardHome

I went from PiHole -> AdGuard -> NextDNS. My patience for tinkering and maintaining wasn't high enough to not just pay someone else to do it :)

Same except skipping AdGuard.

Having the DNS live on a pi sounded like fun for me but it gave me stress due to power outages. There is safety in knowing you aren't adding a point of failure that only you know how to solve.

I also had issues with adding backup DNS, since a backup DNS would be queried if the pihole blocked the DNS query -- so I would have to maintain two seperate blocklists, one local and one offsite.

Post reply on HN