<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Observability on Ivan Versluis — Networknet</title><link>https://networknet.nl/tags/observability/</link><description>Recent content in Observability on Ivan Versluis — Networknet</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 05 Sep 2026 13:55:32 +0200</lastBuildDate><atom:link href="https://networknet.nl/tags/observability/index.xml" rel="self" type="application/rss+xml"/><item><title>DNS with a deliberate path</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="more-than-a-name-lookup">More than a name lookup&lt;/h2>
&lt;p>DNS is a shared dependency for home devices, Kubernetes workloads and internal services. My homelab separates those responsibilities rather than treating every lookup as the same problem.&lt;/p>
&lt;p>Pi-hole provides filtering for LAN clients. Unbound handles upstream resolution. CoreDNS remains responsible for Kubernetes service discovery and selected internal hostname overrides. The purpose is a DNS path that can be explained, constrained and observed—not simply a resolver that answers.&lt;/p></description></item></channel></rss>