<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>plesk obsidian — LowEndSpirit DEV</title>
        <link>https://dev.lowendspirit.com/index.php?p=/</link>
        <pubDate>Thu, 04 Jun 2026 17:32:46 +0000</pubDate>
        <language>en</language>
            <description>plesk obsidian — LowEndSpirit DEV</description>
    <atom:link href="https://dev.lowendspirit.com/index.php?p=/discussions/tagged/plesk-obsidian/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>How to use Cloudns as Secondary DNS provider [ Plesk Tested ]</title>
        <link>https://dev.lowendspirit.com/index.php?p=/discussion/3724/how-to-use-cloudns-as-secondary-dns-provider-plesk-tested</link>
        <pubDate>Thu, 27 Jan 2022 18:02:40 +0000</pubDate>
        <category>Technical</category>
        <dc:creator>hostarts</dc:creator>
        <guid isPermaLink="false">3724@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Hello,</p>

<p>I would like to share our experience regarding Secondary DNS for Plesk server. For the moment It has been pretty straight forward to setup Slave nameservers for Plesk.</p>

<p>The issue is, the solution becomes totally unreliable once you have 2 master servers or more. It looks like Plesk themselves couldn't figure out issues related to rndc-keys etc for our case. We have been getting random disconnections etc...</p>

<p>Additionally it requires the maintenance of the nameservers slave and having them on different locations or datacenters</p>

<p>We found solutions such as gDNS from Admin Ahead but it looks too complicated and not that different from the Plesk Slave servers.</p>

<p>We want to share our solution for the community especially the ones using Plesk, we are also planning to test the solution on different Hosting panels such as cPanel.</p>

<p>You can go ahead and create an account at <a href="https://www.cloudns.net/" rel="nofollow">https://www.cloudns.net/</a></p>

<p>Once done, you will need to put edit a default provided PHP script that you can find on their <a rel="nofollow" href="https://github.com/ClouDNS/cloudns-api-bulk-updates/tree/master/plesk-slave-zones-add" title="Github Page">Github Page</a>.</p>

<p>Due to the multiple changes between the old script and the new one we have provided some additional information to the ClouDNS team who corrected some elements on their previous one.</p>

<p>You can read the article they have put together for Plesk servers. <a href="https://www.cloudns.net/wiki/article/250" rel="nofollow">https://www.cloudns.net/wiki/article/250</a></p>

<p>We will try to do the same for cPanel very soon and update this thread.</p>

<p>through this you can enjoy IPV4 &amp; IPV6 Anycast Secondary DNS and protect your Master server</p>

<p>Regarding the Cronjob to setup we made it run once per minute in our case due to multiple DNS zone changes and new clients. Especially that Plesk is kind of slow when it comes to SSL <img src="https://dev.lowendspirit.com/plugins/emojiextender/emoji/twitter/smile.png" title=":)" alt=":)" height="18" /></p>

<p>We would love to hear your feedback</p>
]]>
        </description>
    </item>
    <item>
        <title>Looking for Plesk Obsidian Shared Hosting (Linux)</title>
        <link>https://dev.lowendspirit.com/index.php?p=/discussion/1998/looking-for-plesk-obsidian-shared-hosting-linux</link>
        <pubDate>Sat, 31 Oct 2020 12:45:47 +0000</pubDate>
        <category>Requests</category>
        <dc:creator>Dewlance</dc:creator>
        <guid isPermaLink="false">1998@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Hello,</p>

<p>I am looking for Plesk Obsidian shared hosting plan.</p>

<p>Requirement:</p>

<ul><li>1GB Disk</li>
<li>1 Domain</li>
</ul><p>Location:  USA, EU or Any Asian Country whichever is cheaper.</p>

<p>Monthly or Yearly.</p>

<p>Thanks.</p>
]]>
        </description>
    </item>
   </channel>
</rss>
