<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pihole on heezy.blog</title><link>https://heezy.blog/tags/pihole/</link><description>Recent content in Pihole on heezy.blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://heezy.blog/tags/pihole/index.xml" rel="self" type="application/rss+xml"/><item><title>Pi-hole on Kubernetes with MetalLB and a Ruckus SSID</title><link>https://heezy.blog/posts/pihole-metallb-ruckus/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/pihole-metallb-ruckus/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;🚧 UNDER CONSTRUCTION 🚧&lt;/strong&gt;
Switch and Ruckus configuration pending. Screenshots to be added.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Pi-hole was already running on the cluster. It worked fine from inside the cluster and via NodePort on weird high ports. The problem was that no actual client device could use it as a DNS server, because DNS clients expect port 53 and NodePort gives you 30054.&lt;/p&gt;
&lt;p&gt;What started as &amp;ldquo;just give Pi-hole a real IP&amp;rdquo; turned into a new VLAN, a new DHCP server, firewall policy changes, switch configuration, and a Ruckus SSID. The usual homelab scope creep.&lt;/p&gt;</description></item></channel></rss>