This article describes how to set up a redundant DNS infrastructure for multiple hosting servers.
The infrastructure described in this example has the following architecture:
The 4PSA DNS Manager will automatically fetch the zones list from every server, so the domains added from the control panel interface will be replicated on the 4PSA DNS Manager server and will have a slave zone.
The recommended 4PSA DNS Manager configuration for this example is:
The exemplification will be made using a Plesk for *nix server.
For this example, the following assumptions are made:
<slave_ip_addr> IP address.<plesk_client_ip_addr> IP address.The steps that have to be followed to set up the Plesk server to dump the zones list are:
STEP 1: Log in as root to the CLIENT1 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/remote/plesk/plesk_export.sh /usr/local/dnsmanager |
STEP 3: Provide the DNS1root 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 path_to_web_srv_root_dir 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 the domain where you want to save the dump is my_plesk.com, then path_to_web_srv_root_dircan be \'/home/httpd/vhosts/my_plesk.com/httpdocs/dnsmanager_dump\'. This directory might be different on your Plesk server.
Make sure that the /home/httpd/vhosts/my_plesk.com/httpdocs/dnsmanager_dump directory exists. Otherwise, the script will not be able to save the dump file.
Do not forget to save the cron file! |
STEP 6: Edit the named.conf file to permit zone transfers from the 4PSA DNS Manager server. In common-allow-transfer named ACL, add the 4PSA DNS Manager server's IP address, like in the example below:
acl common-allow-transfer {
<slave_ip_addr>
};
STEP 7: Since Plesk uses its database to write the named.conf 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 named.conf file will remain correct. To do so, run:
client1# mysql -uadmin -p`cat /ec/psa/.psa.shadow` dnsmanager -e"INSERT INTO misc VALUES(\'DNS_Allow_TransferXX\','<slave_ip_addr>');" |
where:
XX is a unique number (increment it to add more IP addresses).<slave_ip_addr> is the 4PSA DNS Manager server's IP address.STEP 8: Restart the named service:
/etc/init.d/named restart |
The steps that have to be followed to set up the 4PSA DNS Manager server to grab the zones list previously dumped by the Plesk server are:
STEP 1: Using the 4PSA DNS Manager interface, you have to add a Remote update source for the dump location you have just set up. To do so, follow the next steps:
STEP 2: Go to the Clients > {client_name} > Remote Update Locations page.
STEP 3: Using the controls available in the New Remote Update Location fieldset, define a location with the following properties:
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.60.If the specified location is password protected, then you must provide the appropriate HTTP, HTTPs or FTP authentication Username and Password.
STEP 4: Click OK to add the remote location.
In order to integrate multiple servers, you must repeat the above process for all your servers.