For suggestions regarding this manual contact:
docs@4psa.com
Copyright © 2002–2009 Rack-Soft, LLC
All rights reserved
Distribution of this work or derivative of this work is prohibited unless prior written permission is obtained from the copyright holder.
4PSA is a Registered Trademark of Rack-Soft, LLC.
Plesk is a Registered Trademark of Parallels, Inc.
Linux is a Registered Trademark of Linus Torvalds.
RedHat is a Registered Trademark of Red Hat Software, Inc.
FreeBSD is a Registered Trademark of FreeBSD, Inc.
All other trademarks and copyrights are property of their respective owners.
Table of Contents
10 minutes
|
| It will take about 10 minutes to an intermediate user to read this document and follow the steps highlighted here. |
Hardware requirements are strongly related to the expected load and concurrent calls. MySQL server and PHP front-end interface are the most intensive components on a 4PSA DNS Manager server. We recommend quality server hardware with redundant storage system.
Minimum suggested hardware configuration:
4PSA DNS Manager is shipped in ready to install templates, compatible with Virtuozzo and OpenVZ, in standard and EZ format.
4PSA DNS Manager is compatible with the following operating systems:
4PSA DNS Manager is also available in VMware image format, that can be run under VMware Server, VMware Workstation or VMware Player. It can also be converted to run on VMware ESX using VMware Converter. This image is based on CentOS 5.1 operating system.
Installation can be performed in three ways:
What's new in 4PSA DNS Manager 3.6.0 release 090312.03
| [+] System wide templates was added, this type of templates added by admin will be available to all clients. |
| [+] Performance improved on DNS Round Robin monitoring when a lot of resources are monitored. |
| [+] Remote update locations can be now in IDN format. |
| [+] Improved memory footprint on the HTTP server used by DNS Manager by using lighthttpd. |
| [+] It is possible to choose in the interface which is the primary nameserver on a zone (required for some local TLDs). |
| [+] Improved parsing of remote update files. |
| [+] The remote update can be done more often (minimum interval is set to two minutes). |
| [+] In the Remote update locations list the Last Update column is now the date of the last update attempt. Previously it was the date when something was updated, causing confusion. |
| [+] The target from SRV records can be also in other zone. |
| [+] Zone owning mechanism was improved: a zone owned by interface cannot be modified from a Remote Location and vice versa, and a zone owned by a Remote Location cannot be changed from interface (because it's useless). The only features that can be changed from the interface on a zone owned by a Remote Location are: transfer IP addresses, zone SOA, and zone status (enabled / disabled). |
| [+] Export XML is now available from client context. |
| [+] Help system improved, the help is displaying icons from the used skin and the name of the product is no longer displayed when the whitebox license is loaded. |
| [-] Minor interface bugs fixes |
| [-] Fixed random crash of updateurld daemon under 64bit operating systems |
For online help and support please visit the below areas:
Development office:
| Rack-Soft SRL |
| DCL Office Building, 20-22 Bilciuresti Street, sector 1 |
| Bucharest, 014012 |
| ROMANIA |
| Phone: 646-957-8997 (US), 021-3130165 (Romania) |
| Fax: 270-638-0988 (US), 021-3130165 (Romania) |
E-mail: