<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Failover on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/failover/</link>
    <description>Recent content in Failover on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/failover/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DHCP High Availability: Kea HA vs ISC DHCP Failover vs Keepalived&#43;dnsmasq</title>
      <link>https://www.pistack.xyz/posts/2026-05-09-self-hosted-dhcp-high-availability-kea-ha-vs-isc-dhcp-vs-keepalived-guide/</link>
      <pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-09-self-hosted-dhcp-high-availability-kea-ha-vs-isc-dhcp-vs-keepalived-guide/</guid>
      <description>&lt;p&gt;Running DHCP without redundancy is a single point of failure. When your DHCP server goes down, new devices cannot join the network, and existing clients lose their leases at renewal time. For any production environment — from enterprise campuses to homelabs — DHCP high availability is not optional.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
