<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Unbound - vo.rs</title><link>https://vo.rs/tags/unbound/</link><description>Latest from the Unbound desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 11 Jun 2024 11:45:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/unbound/" rel="self" type="application/rss+xml"/><item><title>Split-Horizon DNS: One Domain, Two Answers</title><link>https://vo.rs/story/split-horizon-dns-one-domain-two-answers/</link><description>&lt;p&gt;I run a handful of self-hosted services behind a real domain rather than raw IP addresses, because certificates, bookmarks and muscle memory all want a hostname. The awkward part is that &lt;code&gt;nas.example.com&lt;/code&gt; needs to mean something different depending on who&amp;rsquo;s asking. From outside the house, it should resolve to my public IP so the reverse proxy at the edge can route it. From inside the house, it should resolve straight to the NAS&amp;rsquo;s private address — routing internal traffic out to the internet and back in again just to reach a machine on the same LAN is wasteful at best and broken at worst. Split-horizon DNS is the fix: the same domain name, two different answers, depending on where the query came from.&lt;/p&gt;</description><pubDate>Tue, 11 Jun 2024 11:45:00 +0000</pubDate></item></channel></rss>