• 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.

[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