RPM installation is one of the easiest and most reliable ways to install NamedManager if you are running on a supported platform.

Currently we provided RPMS for:

• RHEL 5 (includes clones such as CentOS & Oracle EL)
• RHEL 6 (includes clones such as CentOS & Oracle EL)

These RPM packages may also work on other RPM-based platforms such as Fedora.

Before installing NamedManager, make sure you have:

a) A functional Apache server setup with PHP 5 installed and SSL enabled.

b) A MySQL database server for storing the application's settings and cache DB.

c) One or more functional bind name servers (can be same or different hosts to the web interface). It is recommended that you use the "bind-chroot" package on RHEL systems.

d) Check the PHP version shipped with your distribution - RHEL 5 ships with PHP 5.1.x by default, ensure that this is upgraded to 5.3 by using the newer PHP packages from amberdms-upgrades OR by installing php53 packages provided by the distribution.

The web interface RPM can be downloaded from two different locations:

a) Directly from Amberdms repository server

• Centos 5 RPMs
• Centos 6 RPMs

Install with:

$ rpm -ivh namedmanager-www-VERSION.rpm

If any dependencies are missing, you may need to download them separately or install them using yum.

b) Using Amberdms repositories with Yum

Using from the Amberdms Yum repository for your specific distribution.

Using the Amberdms Yum repositories enables you to have the latest versions easily installed and dependency resolution will be automatic and is the recommended approach.

Follow the instructions on the repository page to add the repo, then install with:

$ yum install namedmanager-www

When you install the RPM as per the steps above, it will advise you on the command to run to install the database.

This will execute a script that allows you to specific your MySQL root password (if any) and then sets up a new DB and user for NamedManager.

The configuration file will be automatically generated with all the options needed to get up and running by the installer. Note that the installer only contains the minimal key values, most of the options for configuration are exposed via the web interface.

All configuration is in the /etc/namedmanager/config.php file.

By default internal application authentication is used, optionally it can be switched to use LDAP - refer to Installation-Integration-LDAP for instructions on how to do this.

Before you can configure any domain names and records, it's necessary to login to the web interface and configure your name servers.

NamedManager requires all the name servers to have an entry in NamedManager - this information is used to generate NS records for all the domains, as well as being where the API keys are set to allow the name servers to connect to NamedManager for pulling configuration.

The default login is username "setup", password "setup123". The application installs default Apache configuration to run at https://localhost/namedmanager.

For each Bind nameserver being used, the namedmanager-bind RPM package needs to be installed. This step is optional and only needed if you want to use Bind with NamedManager.

This package provides two components:

• Configuration generation script which connects to the NamedManager web interface via SOAP and downloads the latest configuration and writes to Bind zonefiles and config files.
• The log feeder script which installs a bootscript that monitors logs and pushes them back into NamedManager.

The bind integration RPM can be downloaded from two different locations:

a) Directly from Amberdms repository server

• Centos 5 RPMs
• Centos 6 RPMs

Install with:

$ rpm -ivh namedmanager-bind-VERSION.rpm

If any dependencies are missing, you may need to download them separately or install them using yum.

b) Using Amberdms repositories with Yum

Using from the Amberdms Yum repository for your specific distribution.

Using the Amberdms Yum repositories enables you to have the latest versions easily installed and dependency resolution will be automatic and is the recommended approach.

Follow the instructions on the repository page to add the repo, then install with:

$ yum install namedmanager-bind

Read and perform the steps in Installation-Integration-Bind for details on configuring NamedManager to hook into the existing Bind environment.

If planning to use the Amazon AWS Route53 integration, read Installation-Integration-Route53 for instructions on configuration.

You can now begin adding DNS zones - by importing existing Bind zonefiles, generating reverse zones or manual entry.

Use the application configuration panel to set defaults such as SOA contact and expiry times.

If you encounter any technical issues after completing the installation process, please read the Troubleshooting page.