Page History

...

The recommended 4PSA DNS Manager configuration for this example is:

• Server OS: Redhat Redhat Linux, Redhat Enterprise Linux, Fedora Core, FreeBSD 4.9
• Server location: another another network
• Server hardware: a a low end server or a VPS that can work with more than 50,000 zones
• Control panel: no no control panel installed

The exemplification will be made using a Plesk for *nix server.

...

For this example, the following assumptions are made:

• DNS1 is is the 4PSA DNS Manager slave server and has the the <slave_ip_addr> IP IP address.
• CLIENT1 is is a Plesk 7 for *nix server and has the the <plesk_client_ip_addr> IP IP address.

Set Up the Plesk Server to Dump the Zones List

The steps that have to be followed to set up the Plesk server to dump the zones list are:

STEP 1: Log in as as root to the  to the CLIENT1 server server using your favorite SSH console (e.g.:   Putty).

STEP 2: Copy the 4PSA DNS Manager integration tools for the specified control panel (in this case, Plesk for *nix) by running:

client1# mkdir -p /usr/local/dnsmanager
client1# scp -r -p <slave_ip_addr>:/usr/local/dnsmanager/tools/plesk_nix/plesk_zones.sh /usr/local/dnsmanager

STEP 3:  Provide the the DNS1root password password in order to complete the transfer:

client1# chmod 700 /usr/local/dnsmanager/ plesk_zones.sh

STEP 4:  Set up the zones dump cron job. This cronj job will dump the list of the zones on your server to a HTTP accessible location. To do so, run:

client1# crontab -e

STEP 5:  Add the following line to cron:

*/50 * * * * /usr/local/dnsmanager/plesk_zones.sh path_to_web_srv_root_dir/cl1_dump_zones.txt >/dev/null 2>&1

where where path_to_web_srv_root_dir is is the path where the Apache web server stores its public files plus the directory on your domain where you want the dump to be made.

Example: if if the domain where you want to save the dump is is my_plesk.com, then then path_to_web_srv_root_dircan be be \'/home/httpd/vhosts/my_plesk.com/httpdocs/dnsmanager_dump\'. This directory might be different on your Plesk server.

acl common-allow-transfer {
<slave_ip_addr>
};

STEP 7:  Since Plesk uses its database to write the the named.conf file file, the best solution is to add the 4PSA DNS Manager server's IP address to the 4PSA database as well. In this way, you can be sure that the the named.conf file file will remain correct. To do so, run:

client1# mysql -uadmin -p`cat /ec/psa/.psa.shadow` -e"INSERT INTO misc VALUES(\'DNS_Allow_TransferXX\','<slave_ip_addr>');"

where:

• • XX is is a unique number (increment it to add more IP addresses).
  • <slave_ip_addr> is is the 4PSA DNS Manager server's IP address.

STEP 8:  Restart the the named service service:

/etc/init.d/named restart

...

STEP 1: Using the 4PSA DNS Manager interface, you have to add a a Remote update source source for the dump location you have just set up. To do so, follow the next steps:

STEP 2:  Go to the the Clients > {client_name} > Remote Update Locations page page.

STEP 3:  Using the controls available in the the New Remote Update Location fieldset fieldset, define a location with the following properties:

• Remote update location  - Fill in in http://my_plesk.com/path_to_dump/cl1_dump_zones.txt. This is the location where the cron job you have previously set up dumps the zones list file. You must verify that the zones list actually exists at this location.
• Keep minimum <x> minutes between updates  - Use the drop-down list and select select 60.
• Remote URL priority  - If you wish, you can select the priority of the zone definitions downloaded from this URL over other (duplicate) zone definitions.

If the specified location is password protected, then you must provide the appropriate HTTP, HTTPs or FTP authentication authentication Username and  and Password.

STEP 4:  Click Click OK to to add the remote location.

In order to integrate multiple servers, you must repeat the above process for all your servers.

...