For suggestions regarding this manual contact:
docs@4psa.com
Copyright © 2011 Rack-Soft. 4PSA is a registered trademark of Rack-Soft, Inc.
All rights reserved.
Distribution of this work or derivative of this work is prohibited unless prior written permission is obtained from the copyright holder.
DNS Manager is a registered trademark of 4PSA (Rack-Soft, Inc.).
4PSA is a registered trademark of Rack-Soft, Inc.
Linux is a registered trademark of Linus Torvalds.
RedHat is a registered trademark of Red Hat Software, 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 DNS Manager server. We recommend quality server hardware with redundant storage system.
Minimum suggested hardware configuration:
- Intel x86 compatible PC server 2GHz clock speed
- 512 megabytes (MB) of RAM
- 36 GB RAID storage system
- 100 Mbs network card
DNS Manager is shipped in ready to install templates, compatible with Virtuozzo and OpenVZ, in standard and EZ format.
DNS Manager is compatible with the following operating systems:
- Redhat Enterprise Linux Server 5.0 (i386/x86_64)
- Redhat Enterprise Linux (AS/ES) 4 (i386/x86_64)
- CentOS 5.x (i386/x86_64)
- CentOS 4.x (i386/x86_64)
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.4 operating system.
Installation can be performed in three ways:
- Using the Command line installation script (see this article for more details)
- Using the ISO Image (see this article for more details)
- On a Parallels Virtuozzo server (see this article for more details)
- On a VMware Server, VMware Workstation or VMware Player. Also on VMware ESX, deployed with VMware Converter.
Warning
We highly recommend you to read the advices listed below before upgrading to DNS Manager 4.0.0!
-
The check list you have to verify when upgrading from DNS Manager 3.x to DNS Manager 4.0.0 contains the following:
- Do not upgrade to DNS Manager 4.0.0 if your perpetual license is not actively maintained using SUS (Software Update Subscription) or your leased subscription is not current.
- Always use the latest version of the installer available here to upgrade your installation.
- Make sure that your machine hostname resolves, otherwise
daemons will start very slowly. Minimally, you can add to
/etc/hostsa static entry for your machine's hostname. - When trying to use the SOAP engine from PHP over SSL, you might experience connection issues. These are caused by a PHP bug; a workaround is to download the WSDL before loading it into the SOAP connection method. More details are available in the 4PSA Knowledge Base.
- The old SOAP API was renamed to SystemAPI.
What's new in 4PSA DNS Manager 4.0.0 release 110411.05
| [+] Auditing system for actions performed in web interface, command line or SystemAPI |
| [+] Added support for IP6.ARPA zones |
| [+] In the zone export script bind_export.sh it is possible to set zones to be excluded from export file |
| [+] The script bind_export.sh was improved to export NAPTR records, ALLOW_TRANSFER IPs and the NS record for ORIGIN is now marked as primary |
| [+] DNS Manager is now compliant with RFC 4183, it supports both "/" and "-" as delimiter in classless delegation |
| [+] CNAME records that points to a FQDN domain name are only supported in C class reverse zones |
| [+] The MX priorities can be managed also from Global Operations section |
| [+] Multiple records can be added from interface in the same time |
| [+] Wildcards are supported for reverse zones also as specified in RFC4592 |
| [=] Many design and usability issues addressed in the interface |
| [=] Documentation improvements |
| [-] We prevent adding CIDR addresses in "master" directives for slaves zones |
| [-] Added new services for SRV records: caldav, caldavs, carddav, carddavs |
| [-] Fixed EditDnsRecord SystemAPI method to work for IDN domains |
| [-] Fixed ensim_complete.sh export script to support SRV records |
| [-] The "forwarders" statement from /etc/named.conf file was removed on fresh installations to prevent 'named' loops to itself for recursive queries |
Legend:
| [+] new feature |
| [-] bug fixed or removed |
| [=] bug fixed or improved functionality |
For online help and support please visit:
- Support Zone: https://help.4psa.com
- Knowledge Base: http://kb.4psa.com
- Documentation: http://help.4psa.com/docs/
For mailing addresses and phone numbers from our offices:
If you have any question, do not hesitate to contact us.