Selfhosted

40296 readers

185 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Noob question about PiHole (feddit.it)

submitted 10 months ago by Kir@feddit.it to c/selfhosted@lemmy.world

44 comments fedilink hide all child comments

Hy everyone, I have a PiHole instance running on my home server, and I changed my router (Fritz box) DNS in order to use my PiHole. Everything runs great.

I was wondering if I can put another DNS provider on my "alternative DNS server" in my router, in order to have a fallback alternative in case my server is down, or if I should avoid it.

I'm asking this because I don't know if the request will be handled in parallel between the two DNS provider (that would make my PiHole useless) or not. Thank you.

you are viewing a single comment's thread
view the rest of the comments

[–] Kir@feddit.it 3 points 10 months ago (1 children)

This answered my question. Thank you. I guess I will sacrifice redundancy

[–] Froyn@kbin.social 6 points 10 months ago (1 children)

Or set up a second pi-hole.

[–] dorkage@lemmy.ca 3 points 10 months ago (2 children)

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

[–] Lordjohn68@lemmy.world 1 points 10 months ago

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.

[–] Darkassassin07@lemmy.ca 1 points 10 months ago (2 children)

How do you manage automatically transferring the ip of the main rpi to the backup rpi when the first disappears?

[–] dorkage@lemmy.ca 2 points 10 months ago

Keepalived

[–] bigMouthCommie@kolektiva.social -3 points 10 months ago (1 children)

clone the Mac address

[–] Darkassassin07@lemmy.ca 1 points 10 months ago (2 children)

Don't you then run into MAC conflicts?

How do you keep both on the network?

[–] bigMouthCommie@kolektiva.social -2 points 10 months ago

oh. fuck.

Arduino? lol

[–] bigMouthCommie@kolektiva.social -3 points 10 months ago (1 children)

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.

[–] Darkassassin07@lemmy.ca 1 points 10 months ago (1 children)

Then when the main PI returns it creates a conflict...

[–] bigMouthCommie@kolektiva.social -2 points 10 months ago

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