<?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 </title>
    <link>https://peng.fyi/tags/dns/</link>
    <description>Recent content in DNS on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>map[name:Peng Zhang]</managingEditor>
    <webMaster>map[name:Peng Zhang]</webMaster>
    <copyright>Peng Zhang</copyright>
    <lastBuildDate>Wed, 10 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://peng.fyi/tags/dns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Don&#39;t Append a Trailing Dot to Domain Names in Software You Ship to Customers</title>
      <link>https://peng.fyi/post/trailing-dot-dns/</link>
      <pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>
      <author>map[name:Peng Zhang]</author>
      <guid>https://peng.fyi/post/trailing-dot-dns/</guid>
      <description>
        
          
            If you build software that runs in someone else&#39;s environment, anything that isn&#39;t a SaaS you operate yourself, there&#39;s a small, innocent-looking line of code you should think twice about writing:
1hostname = hostname + &amp;#34;.&amp;#34; Appending a trailing dot to a domain name before you resolve it feels &amp;quot;more correct&amp;quot; when you own the domain name. It can even be a performance optimization (more on that later). But in software you don&#39;t control the runtime for, it can result in a hard failure, and you won&#39;t see it in testing, because it only breaks in DNS environments that look nothing like yours.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
