Running a DNS diagnostic tool, like those found at mxtoolbox or pingdom.com, indicates there's problems with your name servers or parent/child relationship.
This occurs because by default we do not configure our Plesk domain templates to use our *.websaversdns.com name servers (ex: ns1.websaversdns.com). While this would be 'correct' DNS practice, we don't configure this way in order to ensure that our resellers are able to better make use of white labeling. The default NS records are typically: ns.yourdomain.com, which do not match the name servers actually entered at the registrar.
In practice this creates no known problems with DNS functionality, yet DNS diagnostic tools love to complain about it.
Resolution
If you wish to avoid having those errors when running DNS diagnostic utilities, you can either:
1. Update your NS records in the DNS Settings for your domain(s) in Plesk to match those entered at your registrar, like ns1.websaversdns.com (be sure to use your actual name servers), or
2. Register your own name servers and ensure they match the NS records in your live DNS zone.
If you wish to avoid having those errors when running DNS diagnostic utilities, you can either:
1. Update your NS records in the DNS Settings for your domain(s) in Plesk to match those entered at your registrar, like ns1.websaversdns.com (be sure to use your actual name servers), or
2. Register your own name servers and ensure they match the NS records in your live DNS zone.
