4PSA DNS Manager 4.0.0 Upgrade Notes

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

4PSA DNS Manager 4 requires MySQL-server 5.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.

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

https://<your_server_IP>:8550

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

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

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

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

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 4PSA DNS Manager interface, or particular named options in place, you MUST reapply them.

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

CRITICAL. Read this only if you are using remote updates. In 4PSA DNS Manager 4, the format of the dump files changed. Two formats are no longer necessary and more information is made available in the new format. Therefore, AFTER upgrading 4PSA DNS Manager to version 4 you will have to replace the interface scripts on ALL remote machines. The interface scripts for more popular control panels are available on:

/usr/local/dnsmanager/remote

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 don't do this, installer will fail.

Considering the above advices, execute:

dnsmanagerinstaller.sh

The script will download 4PSA DNS Manager 4 and will update your current installation. Pay attention to the migration script progress and potential errors.

After installation point your browser to:

https://<your_server_IP>:8550

and