<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Split-Horizon - vo.rs</title><link>https://vo.rs/tags/split-horizon/</link><description>Latest from the Split-Horizon 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>Thu, 01 Feb 2024 13:38:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/split-horizon/" rel="self" type="application/rss+xml"/><item><title>Split-Horizon DNS at Home: One Domain, Two Answers</title><link>https://vo.rs/story/split-horizon-dns-at-home-one-domain-two-answers/</link><description>&lt;p&gt;Here&amp;rsquo;s a problem that arrives the moment you self-host something with a proper hostname. You&amp;rsquo;ve got a service at &lt;code&gt;nextcloud.mylab.local&lt;/code&gt;, or better still at &lt;code&gt;cloud.example.com&lt;/code&gt; using a real certificate, and you want to reach it both from your sofa and from a train. From the train the name has to resolve to your public IP so traffic can find its way in through the router. From the sofa, resolving to the public IP means your packets go out to the internet and try to come straight back in — a manoeuvre called NAT hairpinning that many home routers do badly or refuse to do at all. The clean answer is to give the same name two different addresses depending on who&amp;rsquo;s asking. That is split-horizon DNS, and once you understand why you want it, the how is short.&lt;/p&gt;</description><pubDate>Thu, 01 Feb 2024 13:38:00 +0000</pubDate></item></channel></rss>