29
Noob question about PiHole
(feddit.it)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Jan 2024
29 points (96.8% liked)
Selfhosted
39677 readers
750 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
The issue is that according to the spec the two DNS servers provided by DHCP are equivalent. While most clients favor the first one as the default, that's not universally the case and when and how it switches to the secondary can vary by client (and effectively appear random). So you won't be able to know for sure which client uses your DNS, especially after your DNS server was unreachable for a while for whatever reason. Personally I've "just" gotten a second Pi to run redundant copies of PiHole, but only having a single DNS server is usually fine as well.
This answered my question. Thank you. I guess I will sacrifice redundancy
Or set up a second pi-hole.
I run multiple pinholes using keepalived. Then I only use one DNS in my DHCP server. Second pihole will seemlessly take over if the first one goes down whilst using the original DNS address.
Work quite well. I had to learn the hard way that only using a single pihole was just asking for my partner to be mad when it didn't work / when I was doing server maintenance. Now I have multiple and they can all seemlessly take over if any my server nodes are down
Keepalived is the way. Gravity sync keeps everything in line. Works like a charm. I migrated yesterday from wifi to wired and cannot be happier. As a bonus did not need to reconfigure pivpn.
How do you manage automatically transferring the ip of the main rpi to the backup rpi when the first disappears?
Keepalived
clone the Mac address
Don't you then run into MAC conflicts?
How do you keep both on the network?
oh. fuck.
Arduino? lol
I'm just spit balling here: backup pi pings munute-ly main pi. if main pi is down 2 pings, it resets Mac and reboots network interface.
Then when the main PI returns it creates a conflict...
oh hm...
hmmm
ok. both pis know the live IP and the backup IP, and have the same config: cold boot into backup I and ping live ip