• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Caution: DNS Vulnerability

Is this solution valuable for you?

  • Yes

    Votes: 0 0.0%
  • No

    Votes: 0 0.0%
  • I was not able to reproduce the problem

    Votes: 0 0.0%

  • Total voters
    0
  • Poll closed .
M

MaxemilianH

Guest
The DNS implementation seems to have a problem:
When recursion is enabled for localnets, everybody can query the dns server. This opens the server for DoS attacks, and other vulnerabilities.

How to test
use nslookup on a computer which should not be in a local net
> server <your_server_name_or_ip>
> <any_domain_which_is_not_on_your_dns>

If it returns valid DNS data, your server is open for vulnerabilities


How to fix

Open a command prompt and navigate to the bin directory of your plesk installation
> cd %plesk_cli%

Use the following command to restrict dns recursion to localhost:
> server_dns -u -recursion localhost


Re-test if the server stops answering requests which cannot be answered locally (message should be "Query refused."), but ensure the domains hosted on your machine can be resolved.


To reset this to the default setting:
> server_dns -u -recursion localnets



regards

Maxemilian Hilbrand
www.isicore.de
 
Back
Top