Facebook
Twitter-
Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
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
