Facebook
Twitter-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
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
