Configuring Parallels Pro Control Panel as a Slave Server

To configure Parallels Pro Control Panel as a slave server:

1. Add the external server first before mentioning external DNS server as a master server.
2. Ensure that the external server, and the local-box time is in sync.
3. Ensure that the external server has correct entries for the slave site zone/s(Parallels Pro zones) in its DNS (that is; in named.conf and the zone records), before adding the site/s.
4. Use the external server entry for the master server field, while adding sites/plans/zones.
5. Use the local-name servers/local-box entry for the slave server field, while adding sites/plans/zones. The slave server field is mandatory. Else,
6. Make the local-name servers/local-box permanent, by making their entries as Slave in default plan, before adding new sites.
7. After adding a site, you should see the zone configuration in SOA section as Type - Slave for newly added sites with the IP address of the master server.
8. After adding a site, you should see the created zone/s of newly added sites as Slave in Zone type.
9. You can Add/Edit/Delete records of an existing slave zone from Parallels Pro server, and these changes will gets transferred to a external master server. (rndc transfer)
10. If there are changes in the zone/s of the external master server, you should see the updated records in the respective zone/s of slave Parallels Pro Control Panel server.
11. If there are changes in the zone/s of the external master server, you can update records on slave zone of the Parallels Pro Control Panel server by doing the Refresh action for a particulate slave zone.

Note: The ISP/Reseller should see the notification sent by master server in /var/log/message, each time there is a change in zones of the master.