<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DNS on Ivan Versluis — Networknet</title><link>https://networknet.nl/tags/dns/</link><description>Recent content in DNS on Ivan Versluis — Networknet</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 06 Sep 2026 10:45:43 +0200</lastBuildDate><atom:link href="https://networknet.nl/tags/dns/index.xml" rel="self" type="application/rss+xml"/><item><title>DNS visibility starts on the LAN</title><link>https://networknet.nl/notes/pihole-encrypted-dns/</link><pubDate>Sat, 05 Sep 2026 12:00:00 +0200</pubDate><guid>https://networknet.nl/notes/pihole-encrypted-dns/</guid><description>&lt;h2 id="start-with-the-questions-leaving-the-network">Start with the questions leaving the network&lt;/h2>
&lt;p>DNS is one of the clearest ways to understand what is happening on a home network. Almost every device resolves a name before it reaches a website, cloud service, update server or telemetry endpoint. When every client uses a different external resolver, that behavior remains fragmented and difficult to explain.&lt;/p>
&lt;p>My first objective is therefore simple: give LAN clients one local DNS entry point with Pi-hole. Centralizing resolution creates visibility before adding more advanced controls. It shows which clients are active, which domains they request, what is being blocked and where resolution fails.&lt;/p></description></item></channel></rss>