• 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.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

[bug]W2k3 DNS: Plesk adds an obsolete third nameserver

H

humanity

Guest
When a domain is created, Plesk seems to add an extra zone to Windows DNS: one which is obsolete and invalid.
it's a ns record, with as value the name of the server you are running. So for instance, you have two ns records:

ns1.myhostingcompany.com
ns2.myhostingcompany.com

a third ns occurs, one which is not viewable in the Plesk dns template.
When your server is named 'dedi1', a ns record 'dedi1' will be added with each domain you add with Plesk.

I reported this ages ago, still no fix. You guys should check it out. It's easy to reproduce.

intodns.com can confirm my report.

"WARNING: At least one of your NS name does not seem a valid host name"
 
Back
Top