Facebook
Twitter-
Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
To get into the festive spirit, install the Skins extension. -
The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
-
The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
-
The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.
endless upgrade to flesh out the DNS errors?
- Thread starter Oddst
- Start date
What is problem? Where it is described and correctly reported? Do you mean this issue http://kb.parallels.com/en/113119 or what?
The problem is my additude.
I don't know why I'm so irritated by this but when I updated in Nov, Plesk overwrote my DNS default template and it caused me major headaches. Since then, I've been bitter about the software. I would switch to something else, but haven't had the time or motivation to migrate to another CP/Server yet. Basically, it appeared i was being forced to include a random NS instead of being allowed to use NS1, NS2.
The solution you provided did not exist when the problem first arose, so I overlooked the omitted dns record. That set me straight, and I see where my mistake was.
I suspect I could delete the ns record(s) at this point, and it would work fine, so thanks for setting me straight.
I don't know why I'm so irritated by this but when I updated in Nov, Plesk overwrote my DNS default template and it caused me major headaches. Since then, I've been bitter about the software. I would switch to something else, but haven't had the time or motivation to migrate to another CP/Server yet. Basically, it appeared i was being forced to include a random NS instead of being allowed to use NS1, NS2.
The solution you provided did not exist when the problem first arose, so I overlooked the omitted dns record. That set me straight, and I see where my mistake was.
I suspect I could delete the ns record(s) at this point, and it would work fine, so thanks for setting me straight.
Last edited:
Similar threads
