<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Thinking about moving DNS]]></title><description><![CDATA[<p dir="auto">Hey,<br />
as netcup's dnssec is still a mess I'm thinking about moving the DNS part (not the domains themselves) to deSEC (offering API as well).<br />
Is it possible in cloudron to change the dns provider of an existing domain on the fly? meaning: i change the provider and API and cloudron automatically creates all the entries with my new DNS provider?</p>
]]></description><link>https://forum.cloudron.io/topic/16001/thinking-about-moving-dns</link><generator>RSS for Node</generator><lastBuildDate>Sat, 26 Sep 2026 09:23:01 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/16001.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 23 Sep 2026 19:22:17 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Thinking about moving DNS on Thu, 24 Sep 2026 07:12:22 GMT]]></title><description><![CDATA[<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/joseph" aria-label="Profile: joseph">@<bdi>joseph</bdi></a> <a href="/post/129937">said</a>:</p>
<p dir="auto">As a heads up, deSEC has some lots of rate limits (reported elsewhere in the forum). So, if you have lots of subdomains with dynamic DNS you hit these limits.</p>
</blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/sponch" aria-label="Profile: sponch">@<bdi>sponch</bdi></a> see <a href="https://forum.cloudron.io/topic/15848/throttling-issue-error-429-with-dyndns-auto-update-and-desec.io-avoidable">here</a> for the details of rate limiting with DeSEC for example (there are a few other threads on the forum too)</p>
<p dir="auto">However, I also need to point out that this is avoidable (at least to an extend). I have made exactly what I suggested in the mentioned thread:<br />
A dedicated script pooling and updating deSEC DNS records in batch instead of a one call for each. This, so far, as worked just fine.</p>
]]></description><link>https://forum.cloudron.io/post/129940</link><guid isPermaLink="true">https://forum.cloudron.io/post/129940</guid><dc:creator><![CDATA[Teiluj]]></dc:creator><pubDate>Thu, 24 Sep 2026 07:12:22 GMT</pubDate></item><item><title><![CDATA[Reply to Thinking about moving DNS on Thu, 24 Sep 2026 06:42:03 GMT]]></title><description><![CDATA[<p dir="auto">As a heads up, deSEC has some lots of rate limits (reported elsewhere in the forum). So, if you have lots of subdomains with dynamic DNS you hit these limits.</p>
]]></description><link>https://forum.cloudron.io/post/129937</link><guid isPermaLink="true">https://forum.cloudron.io/post/129937</guid><dc:creator><![CDATA[joseph]]></dc:creator><pubDate>Thu, 24 Sep 2026 06:42:03 GMT</pubDate></item><item><title><![CDATA[Reply to Thinking about moving DNS on Wed, 23 Sep 2026 19:33:35 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/sponch" aria-label="Profile: sponch">@<bdi>sponch</bdi></a><br />
it should work but with DNS propagation you might run into DNS cache issues.<br />
So similar to <a href="https://docs.cloudron.io/backups#steps" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.cloudron.io/backups#steps</a> you could edit your hosts file to override DNS records to ensure you still have access.<br />
With that changing from A to B DNS provider should always work and with the Sync DNS button it will create all records.</p>
]]></description><link>https://forum.cloudron.io/post/129925</link><guid isPermaLink="true">https://forum.cloudron.io/post/129925</guid><dc:creator><![CDATA[james]]></dc:creator><pubDate>Wed, 23 Sep 2026 19:33:35 GMT</pubDate></item></channel></rss>