Page History

This article describes how to set up a redundant DNS infrastructure for multiple hosting servers.

Infrastructure

...

architecture

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.

Requirements

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

...

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

Assumptions

For this example, the following assumptions are made:

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

...

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

...

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

...

/etc/init.d/named restart

Setting

...

up the 4PSA DNS Manager

...

server to

...

grab the zones list from the Plesk

...

server

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:

...

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

Related

...

articles