In this Video:
I’m diving into something super important, setting up a highly available Pi-hole DNS server. We’re doing it without GravitySync (RIP to that tool as it’s soon to be deprecated), and instead, we’re using Orbital Sync to keep our block lists and DNS settings in check across two Pi-hole instances. Then, we’ll set up Keepalived to make sure our DNS is always available, even if one Pi-hole goes down. Perfect for all you HomeLab fans out there!
———————————————————|
Links from the video:
Github:
Pihole:
Proxmox Helper Scripts:
Orbital Sync:
———————————————————|
Connect with me:
Github:
———————————————————|
Music from the video:
Generated with Suno.ai
——————————————————–|
Timestamps:
00:00 – Intro and project overview
01:05 – Why GravitySync is deprecated (and what we’ll use instead)
02:00 – Overview of Pi-hole setup (VMs, Containers)
03:40 – Setting up Pi-holes (using Proxmox scripts)
05:55 – Introduction to Orbital Sync (an alternative to GravitySync)
06:45 – Docker Compose setup for Orbital Sync
08:30 – Running and testing Pi-hole sync
10:25 – What makes a Pi-hole setup “high availability”?
11:30 – Installing and configuring Keepalived
12:45 – VRRP explained (virtual IP failover setup)
14:10 – Setting up priority and virtual IP for Pi-hole failover
15:55 – Final testing: Simulating a DNS failover
16:25 – Conclusion and future plans
[ad_2]
source
