An in-depth discussion of DNS failover, what it is, and why you need this configured in your home lab environment along with production. We discuss and look at three different designs for DNS failover and which design you might use for which use cases and what components and solutions are involved. This will help to take your home lab name resolution resiliency to the next level! We will look at things like Pi-Hole, Unbound, Windows Server DNS, Nebula Sync and more. Written blog on this topic: Proxmox server build 2025!!!!!! (amazon affiliate links I get a small commission): Minisforum BD795M – RackChoice 2U Micro ATX Compact – Cooler Master MWE Gold 850 V2 – Crucial 128 GB 5600MT/sec RAM – Noctua NH-L9i-17xx, Premium Low-Profile CPU Cooler – Crucial 96GB kit of DDR5 SODIMM memory kit – Intel X520-DA2 10 GbE network adapter – Kingston 240 GB drive for boot – Samsung EVO 990 Pro 2TB – MX-4 Thermal paste – Case fans: Check out the VHT forums to get your questions answered: ★ Subscribe to the channel: ★ My blog: ★ Twitter: ★ LinkedIn: ★ Github: ★ Facebook: ★ Discord: ★ Pinterest: Introduction to DNS and failover - 0:00 What is DNS failover? 0:49 Load balance vs failover - 1:35 Running local authoritative domains in home lab - 1:50 Option 1 for DNS failover - 2:43 Using Windows Domain Controllers with DNS - 3:30 Downstream Unbound server - 3:41 Automatic DNS registration with secure updates - 4:10 Different virtual hosts and storage - 4:32 Client LAN network 2 Pi-Hole servers with Nebula-sync - 4:49 Hybrid Option 1 with 2 Pi-Hole servers and Keepalived - 5:27 Single IP address to hand out to clients for failover - 6:06 Local DNS server and one public DNS server - 6:45 Showing this configuration with one local and public and behavior with local domain - 7:38 Option 3 is just using public DNS resolvers - 8:40 Designing using public resolvers and spreading your config between providers - 9:00 Configuring DHCP scope options for both DNS resolvers - 9:40 Wrapping up thoughts on DNS failover - 10:20