<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dhcp on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/dhcp/</link>
    <description>Recent content in Dhcp on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/dhcp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DHCP Server Management — Kea vs dnsmasq vs ISC DHCP</title>
      <link>https://www.pistack.xyz/posts/2026-05-04-self-hosted-dhcp-server-management-kea-dnsmasq-isc-dhcp-guide/</link>
      <pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-04-self-hosted-dhcp-server-management-kea-dnsmasq-isc-dhcp-guide/</guid>
      <description>&lt;p&gt;Dynamic Host Configuration Protocol (DHCP) is the invisible backbone of every network. Every device that connects — laptops, phones, IoT sensors, servers, printers — relies on DHCP to get an IP address, DNS server information, and network configuration parameters. Yet most organizations treat DHCP as an afterthought, relying on their router&amp;rsquo;s built-in server or basic configuration files with no monitoring, no centralized management, and no visibility into address allocation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
