https://samily.it/tags/networking/Recent content in Networking on SamilyITHugoenThu, 29 Oct 2026 00:00:00 +0100https://samily.it/posts/opnsense-ddclient-ttl/Wed, 11 Sep 2024 00:00:00 +0200https://samily.it/posts/opnsense-ddclient-ttl/<div class="flex rounded-md bg-primary-100 px-4 py-3 dark:bg-primary-900"> <span class="pe-3 text-primary-400"> <span class="icon relative inline-block px-1 align-text-bottom"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path fill="currentColor" d="M506.3 417l-213.3-364c-16.33-28-57.54-28-73.98 0l-213.2 364C-10.59 444.9 9.849 480 42.74 480h426.6C502.1 480 522.6 445 506.3 417zM232 168c0-13.25 10.75-24 24-24S280 154.8 280 168v128c0 13.25-10.75 24-23.1 24S232 309.3 232 296V168zM256 416c-17.36 0-31.44-14.08-31.44-31.44c0-17.36 14.07-31.44 31.44-31.44s31.44 14.08 31.44 31.44C287.4 401.9 273.4 416 256 416z"/></svg> </span> </span> <span class="dark:text-neutral-300"><strong>Update October 2026:</strong> Since os-ddclient 1.18, new installations use the <em>native</em> backend by default. It does not use <code>ddclient.conf</code>, so the script below only works with the <em>ddclient</em> backend (Services &gt; Dynamic DNS &gt; Settings &gt; General settings &gt; Backend). Since os-ddclient 1.26, the TTL can be set directly in the GUI for Gandi and GoDaddy.</span> </div> <p>Unfortunately, in OPNsense, it is not possible to set the TTL (Time to Live) for Dynamic DNS, which means DNS entries always have a TTL of 10800 seconds or 3 hours. This limitation undermines the purpose of Dynamic DNS, in my opinion.</p>