[Plesk 11 - End user] Disabling or Enabling DNS Recursion on Your Linux Server with Plesk Control Panel

Overview 

DNS recursion is enabled by default on your Linux Server with Plesk Control Panel. With recursion enabled, the DNS server queries other DNS servers on behalf of the requesting client to fully resolve the name, before sending the answer back to the requesting client. Since this setting can increase your vulnerability to a DNS amplification attack, you should disable this option on your server if your DNS server is not intended to receive recursive queries.

This article explains how to enable or disable DNS resolver on your Linux Server with Plesk Control Panel.

Instructions 

1) Connect to your server via Plesk Control Panel using your credentials. You can locate your credentials via your Control Panel ( https://manage.myhosting.com) under the Parallels Plesk Panel tab.

2) After connecting to your server, navigate to Tools & Settings and locate the DNS Template under the General Settings.

 

3) Next, click on DNS recursion settings.

 

4) Choose the required setting as explained below for your DNS recursion. The default setting is Localhost.

Any host allows internal and external DNS recursions.

Localnets allows the full subnet that your server’s IP address is located on. For example, if your server’s IP address is 168.144.1.85/24, your server will allow DNS recursion for all IP addresses between 168.144.1.0 to 168.144.1.255 and also 127.0.0.1

Localhost only allows the loopback IP address and also the server’s assigned IP address to use DNS recursion.

5) After making the necessary changes, you need to restart your DNS server to apply the changes. Click on Tools & Settings again and find Service Management within the Server Management section.

 

6) Find DNS Server (BIND) under your Services and click on the yellow restart button.

 

After following the instructions above, you should now have successfully changed the settings of your Bind Server’s DNS recursion via the Plesk Control Panel.

 

Was this article helpful?
0 out of 0 found this helpful