Release Notes

In this section you will find the changelogs for DNS Manager 5 and later releases.

Requirements

For details with regard to the minimum hardware requirements and compatibilities, please consult the Hardware Compatibility List.

Installation

The DNS Manager installation can be performed:

• Using the Command line installation script (check the Command Line Installer section for more details);
• Using the ISO Image (check the ISO Image Installation section for more details);
• Using a Virtuozzo server (check the Virtuozzo Templates Installation for more details).

Changes in DNS Manager 5 Series

Before upgrading a DNS Manager 1.4.0 installation to DNS Manager 5.2.5, you must be aware of the following important changes in DNS Manager 5.2.5:

Running Beside Plesk

DNS Manager cannot run on the same server with Parallels Plesk. DNS Manager is still able to gather records from Plesk servers, but the DNS Manager server is no longer able to run on the same server with Plesk. If you are currently running DNS Manager 1.x on a Plesk server, you have to migrate your installation to another machine.

MySQL Update

DNS Manager requires MariaDB-server 10.x. During the installation it will update your current MySQL server. If you are using this machine for other purposes (although not recommended) be aware that this might affect applications that require MySQL.

Management Interface

DNS Manager runs on its own admin server. You will be able to access the management interface after update to:

https://<your_server_IP>

Syncronization Daemons

In order to synchronize with database zones and remote updates, DNS Manager uses two daemons, called zonemngd and updateurld. The cron jobs in DNS Manager are no longer available. Please refer to the Command Line Interface guide for more details.

Package Distribution

DNS Manager comes in RPM packages, on Linux distributions that support RPM. The product installer will download and install them from the DNS Manager repository.

Before Upgrading

This is the checklist you need to verify when upgrading DNS Manager:

Assure Redundancy

Upgrading to DNS Manager will stop your named/bind server. Do not upgrade a DNS Manager server if redundancy is not guaranteed by secondary servers. Therefore all servers in the infrastructure must be updated one at a time.

Prior to 1.3.5

The upgrade script will upgrade ONLY DNS Manager 1.3.5 and newer server versions. If you have installed an older version, upgrade it to DNS Manager 1.4.0 and then run the DNS Manager 5 installer.

Root Access

Make sure that the MySQL user setup in DNS Manager 1.x configuration file at /usr/local/dnsmanager/dnsmanager.conf has root access to your MySQL installation. If root access is not available, grant it with root access before executing the installer. If you do not do this, installer will fail.

Named Server Reconfiguration

Named server will be totally reconfigured during this upgrade. Your old named files will be saved to /var/named/run-root.4psasave. If you had any zones that were not managed in DNS Manager interface, or particular named options in place, you MUST reapply them.

Check Permission and Limits

The upgrade process will import records from your old database and convert them to the new DNS Manager format. After upgrade, you should check permissions and limits on your customers, because DNS Manager features more advanced permissions and limits, some of them with a slightly different behavior.