Live data from Hacker News

Setting up a secondary Pi-Hole on my home network

dzombak.com

61–70 of 75 posts

Re: Setting up a secondary Pi-Hole on my home network

#61

If anyone wants a redundant system and is happy not to self-host, then I can recommend NextDNS. Works great, but not free over a certain number of requests. Can’t speak to its privacy levels though - as with anything, assume records will be supplied to authorities when required. But overall it has been great - provides network wide DNS filtering and has clients for mobile and desktop devices! With a good dashboard, r…

NextDNS seems to be maintaining its DNS infrastructure, but the mobile apps are almost abandoned and don’t even work many a times. The NextDNS forums have a lot of posts without any assistance or response from the main team.

To me, it seems like the founders are not focused on customer support or making the NextDNS ecosystem better.

Re: Setting up a secondary Pi-Hole on my home network

#62

Earlier quoted context omitted.

Obviously the fourth instance should be hosted on AWS connected to your local Tailnet.

But what if AWS has an outage as well?

Are you really web scale if you aren't multi-cloud with accounts in GCP and Azure?

Re: Setting up a secondary Pi-Hole on my home network

#63
I have two PiHole instances plugged on opposite sides of the house. Instead of the mentioned GravitySync, I just occasionally copy the backup file from the primary to the secondary pihole instance (both of which are dockerized on Raspberry Pi hardware)

Works great. Rarely need to think of it. I recommend looking up the recommended whitelist and adding anything there that looks relevant to you.

Last downtime was a month ago when external circumstances forced me to move both servers. Yhe RPi, lacking a real time clock or its neighbor to bootstrap DNS, couldn't get the current time ir dns, and thus had out-of-date certificates for dnssec... Solution was to add the direct ip address to an NTP server temporarily to the list of websites to use for NTP.

Re: Setting up a secondary Pi-Hole on my home network

#64
> Having a single DNS server for your network is very stressful

Common... He's talking about a home network.

I also have one of my Pi set up as a DNS server (running unbound directly not PiHole though) and this thing is rock stable solid.

We're talking about Linux here. I've had a Linux server reach years of uptime (kids: don't try this at home, it's not secure but it was a test of Linux's stability).

Redundancy is great though but I really wouldn't lose sleep over it. If anything you can "dd" the Pi's SD card to another one and just replace the Pi (or the SD card) should anything go wrong.

Re: Setting up a secondary Pi-Hole on my home network

#65

This line/'service'; Really?! Why? Finally, since 32GB is a relatively small disk, I installed a daily cron job to clean the apt cache[0]: Which is a Debian package to run `apt-get clean` that the author of the blog created. Here you go, no package required: # printf 'apt-get clean\n\n' > /etc/cron.daily/daily-apt-clean && chmod +x /etc/cron.daily/daily-apt-clean` [0] - https://github.com/cdzombak/apt-daily-clean

Way back this was a solid way of systems management, write a collection of packages that did things and then system config would be a matter of installing a list of packages.

System as declarative configuration? It sure does seem we've been spinning in circles for the past few decades, creating a complexity stack of failed attempts at solving the same problems.

Wonder how much of that is social. E.g. processes and function calls are effectively equivalent: command line arguments are effectively positional or named parameters, while environmental variables are equivalent to dynamic binding - a powerful technique all but excised from programming languages, except for the Lisp family. And yes, this makes the shell a REPL. The main difference between a program and a function then feels like the relationship with programmers: a program is expected to be a named thing to distribute and sign with your name; a function is more ephemeral. But does this difference warrant having each in a separate, distinct, complex layer?

Re: Setting up a secondary Pi-Hole on my home network

#67

Earlier quoted context omitted.

There's a lot of advertising activity that ublock doesn't catch, but Pi-Hole does. Usually it's tracking APIs rather than ads themselves. It's also useful for clients where I can't install client-side adblocking, ie smart TVs (which try to phone home a _ton_ of advertising/analytics information). I also don't use client-side adblock on my work laptop (can't install unapproved extensions) nor my iPhone, so Pi-Hole sti…

Your work laptop allows use of local DNS? Lucky you! My work laptop gets to hit all the trackers.

Back when I was working (a few years ago now), my company laptop had some lame Cisco DNS proxy installed in the name of "security." The laptop ignored the DNS servers provided by DHCP and the proxy used a pinned company DNS server. Any DNS requests that could not be resolved would redirect to some questionable server on the open Internet that also happened to have an ssh server on port 22.

None of this bothered me until the time I tried to ssh into one of my local boxes, was and redirected to the bogus server, which prompted me for my password, which I stupidly provided out of habit.

So now some random server on the open Internet has collected the hostname, username, and password for my local machine. I reported this to the company IT department and their response was a shrug.

Re: Setting up a secondary Pi-Hole on my home network

#68
I have AdGuardHome running in a Docker on the PVE that also hosts my router (OpnSense) in a VM. They both have an uptime of 341 days (which was the last time I did a scheduled kernel upgrade on the host machine). There is no reason for a redundant DNS server on a typical home network.

Re: Setting up a secondary Pi-Hole on my home network

#70
post #31

> I have never used macvlan (or ipvlan) networking with Docker, I don’t know how to set it up, and I’ve read conflicting and confusing reports about how easy it is to use with Pi-Hole macvlan is cool in theory. it lets you broadcast a "real" MAC address through your container's veth. this allows it to get a real IP from your router. you can even use VLAN trunking to assign the MAC to a VLAN on your physical NIC. that…

> macvlan can help get you slightly better networking performance

Negligible on anything what can run Docker ATM.

The main benefit is what you really get the real MAC which:

totally skips Docker NAT shenanigans

provide a single MAC/IP on any node, which is useful for the single instance/multiple nodes/ shared storage situations

Post reply on HN