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

161–170 of 316 posts

Re: Pi-hole v6

#161

Post by eldaisfish »

brummm wrote: post #137
martin_a wrote: post #132

Earlier quoted context omitted.

I think my PiHole is up for 3+ years on a Raspberry Pi dedicated to that task. Did not fail once since then, so not sure if "DNS is going down" is really an issue. But maybe I've got survivorship bias.

Living in a North American city with power wires being above ground, I have had so many power outages in the last five year, it was kind of a crazy thing to get used to. My Pi would not deal well with power outages when running through the SD card and so I stopped using it.

I've had a raspberry pi and pihole going on the same SD card for approximately seven years now.

I also regularly reboot the pi by simply cycling power.

The solution was fairly simple. Send the linux log files to /dev/null (or whatever it is actually called, i.e. RAM) and disable query logging in pihole.

That's it. Helps greatly!

Re: Pi-hole v6

#162

Post by master_crab »

jimsmart wrote: post #103
paxys wrote: post #95

Earlier quoted context omitted.

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.

> 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. That depends entirely on what capabilities your router has. Many routers have a setting for the DNS info they give to clients via DHCP, which would mean every client is indeed using PiHole directly for DNS resolution. Other less capable routers, onl…

And if your gateway device is configurable enough you can ban or redirect port 53 requests (DNS) to whatever machine you would like to use to serve up resolution.

Re: Pi-hole v6

#163

Post by btreecat »

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…

There's also adguard home

https://adguard.com/en/adguard-home/overview.html

Re: Pi-hole v6

#164

Post by NoPicklez »

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…

You'd be hard pressed to find that an auditing mode would be helpful. Even once you hit that big red button, depending on the blocklists you use you will come across false positives that cause issues.

Re: Pi-hole v6

#165

Post by sneak »

paxys wrote: post #95
MyOutfitIsVague wrote: post #38

Earlier quoted context omitted.

> 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.

Not all routers proxy DNS; many have DHCP settings so you can give the pi-hole’s address as DNS server to clients via DHCP.

I imagine this is how it’s usually done. There’s no reason to double proxy.

Re: Pi-hole v6

#166

Post by sneak »

timoteostewart wrote: post #67
josephg wrote: post #34

Earlier quoted context omitted.

> For my "smart tv" which I begrudgingly have to allow on my network occasionally for software updates Why install software updates if you don’t use the “smart” features? Our smart tv has been banned from the internet for years.

I imagine software updates might bring improved support for various media codecs, or UI enhancements, or better Bluetooth compatibility, etc.

I let one of my cheap smart TVs update for this reason (and not the other two identical ones I have) and now that one crashes and lags all the time, despite none of them being on the internet.

Embedded device software development quality is usually even worse than webapp software development quality.

Re: Pi-hole v6

#167

Post by distances »

mrmuagi wrote: post #140
martin_a wrote: post #132

Earlier quoted context omitted.

I think my PiHole is up for 3+ years on a Raspberry Pi dedicated to that task. Did not fail once since then, so not sure if "DNS is going down" is really an issue. But maybe I've got survivorship bias.

I live in Vancouver BC, we have a power outage every 1-2 years due to high winds or fallen power poles. I noticed some devices on my home network whilst connected to power have power quality issues too, no doubt a UPS would help here.

What's the concern about power outages? My Pi-hole is back online much faster than my router.

Re: Pi-hole v6

#168

Post by lukevp »

alabastervlog wrote: post #127
b3lvedere wrote: post #69

Earlier quoted context omitted.

Is this really true? The margin must be huge. I've seen 4K smart tv's for half the price of 4k monitors.

I've had a little insight into this world. To make the BOM costs work at the retail prices they charge for things like common set-top streaming boxes (e.g. Roku) and, now, TVs themselves since they incorporate the same stuff, they have to be selling data. Otherwise they're selling at a loss, once you factor in middleman margins and such. You can try to compete by charging a reasonable amount for your hardware and sof…

Or you buy an Apple TV, that’s priced appropriately with its capabilities and doesn’t thieve everything from your network and your house.

Re: Pi-hole v6

#169

Post by CharlesW »

hk1337 wrote: post #50
eamag wrote: post #6

Want to highlight https://nextdns.io/ as a similar service, very happy with it

This actually seems rather nice. Not the same as PiHole but I can see its upsides. One upside I like about PiHole is that I can set it up to distribute the DNS to all my devices. This seems like I have to manually configure each device? ATT doesn't let you set the IPv6 DNS, so I either have to disable IPv6 on the network or setup PiHole to pass IPv6 and the DNS I want to the device.

> This seems like I have to manually configure each device?

You don't have to (and I assume most users don't), but you can if you want per-device reporting. You just set your router's DHCP server to hand out NextDNS's DNS servers.

Re: Pi-hole v6

#170

Post by OJFord »

hotstickyballs wrote: post #157
guhcampos wrote: post #154

Earlier quoted context omitted.

I think [1] is quite irrelevant to be honest. Blocking DNS isn't a destructive operation. I've been using pi-hole for years and I simply block everything and cherry-pick a few exceptions here and there when something breaks. I only had to really troubleshoot maybe 3-4 times in years, and half of that were related to the fact I worked for companies that had domains blocked.

It's destructive if you can't reach your remote devices anymore. See also jeff geerling's "It was DNS T-Shirt" https://www.redshirtjeff.com/shop/p/it-was-dns-shirt

Only if they're configured to explode if not pinged for 30s or something.
Post reply on HN