• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

[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