<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Pihole on Aperture Zone</title>
    <link>https://aperturezone.com/tags/pihole/</link>
    <description>Recent content in Pihole on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/pihole/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pi-hole &#43; Unbound: DNS filtering for the guest network</title>
      <link>https://aperturezone.com/posts/pihole/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/pihole/</guid>
      <description>&lt;p&gt;It’s a situation many of us are familiar with. You throw a barbecue, the kids show up with their smartphones, and the first thing they ask—before even saying hello—is, “What’s the WiFi password?” You give them the 25-character guest network password with 4 case-sensitive characters just to hear them complain, and sure enough, the “hello” is gone, but that’s my little revenge&amp;hellip; Otherwise, isolated from the LAN, internet access only, dedicated VLAN—the infrastructure is clean.
Except you have no control over what they’re browsing.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
