<?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 David Hrbáč</title>
    <link>https://www.hrbac.cz/tags/dns/</link>
    <description>Recent content in dns on David Hrbáč</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 26 Aug 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://www.hrbac.cz/tags/dns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rancher: Migrating server-url to a new domain with split-horizon DNS</title>
      <link>https://www.hrbac.cz/2026/08/rancher-migrating-server-url-to-a-new-domain-with-split-horizon-dns/</link>
      <pubDate>Wed, 26 Aug 2026 12:00:00 +0000</pubDate>
      
      <guid>https://www.hrbac.cz/2026/08/rancher-migrating-server-url-to-a-new-domain-with-split-horizon-dns/</guid>
      
      <description>I recently migrated a Rancher installation from an old domain name to a new one. The setup was slightly more interesting than a simple DNS rename because Rancher was used from different network locations and the environment used split-horizon DNS.
The simplified topology looked like this:
local downstream clusters -&amp;gt; internal RR DNS -&amp;gt; Rancher ingress -&amp;gt; internal/self-signed CA remote downstream clusters -&amp;gt; public DNS -&amp;gt; F5 VIP -&amp;gt; public CA certificate users -&amp;gt; public DNS -&amp;gt; F5 VIP -&amp;gt; public CA certificate As an ASCII diagram:</description>
      
    </item>
    
  </channel>
</rss>
