I have two servers both running CentOS 4.2. The primary server has Ensim Pro 10.0.0-13.rhel.4ES (I will be upgrading to 10.1.x shortly, most likely) and currently has the primary name server (ns1.domain.com) and a virtual DNS (setup as ns2.domain.com). The second server has cPanel/WHM and has the option to cluster servers and create a trust relationship in order to update and synchronize DNS zone records. I am curious as to what I need to do in order to establish this so that the cPanel server can function as my secondary DNS server to my primary Ensim DNS server. Obviously this may not be possible, in that case, what is the proper procedure for establishing this. Am I heading in to more of a headache than its worth?

I have two servers both running CentOS 4.2. The primary server has Ensim Pro 10.0.0-13.rhel.4ES (I will be upgrading to 10.1.x shortly, most likely) and currently has the primary name server (ns1.domain.com) and a virtual DNS (setup as ns2.domain.com). The second server has cPanel/WHM and has the option to cluster servers and create a trust relationship in order to update and synchronize DNS zone records. I am curious as to what I need to do in order to establish this so that the cPanel server can function as my secondary DNS server to my primary Ensim DNS server. Obviously this may not be possible, in that case, what is the proper procedure for establishing this. Am I heading in to more of a headache than its worth?

Once you upgrade to Ensim v10.1 you will be able to define other external name server(s).

To add an external DNS server:

In the shortcuts section of the Home page, click External Servers (DNS section). The External Server List form opens displaying the list of external servers.

Click Add External Server.

In the Host Name field, enter the name of the server. For example, ns1.isp.net.

In the IP Address field, enter the IP address of the server. For example, 65.65.65.65.

In the Key Name field, enter the key name of the transaction signature that authenticates zone transfers for the external server. For example, wp_default_key. (note that the dot is part of the key name).

In the Secret field, enter the secret value of the transaction signature that authenticates zone transfers for the external server. For example, IC6GU6asxPceF72LjQTfUQ==.

Note: Usually, BIND name servers are configured to secure the zone updates using a transaction signature (TSIG) that uses a key/secret value pair. If your external server is running BIND, and is configured to protect zone updates using a key/secret value pair, enter the name of external server's key/secret value pair here. If your external server is also running Ensim Pro, the key name you need to enter is wp_default_key. (the dot is part of the key name). The secret corresponding to that key can be obtained from the SOA Settings page on the control panel.

However, if your external name server is running another implementation of DNS, such as Microsoft DNS, chances are that it does not support the TSIG method of protecting zone updates. In this case, the external server must be configured to allow zone updates from your Ensim Pro server, otherwise, the Ensim Pro server will not be able to add records to any zone existing on the external name server.

Click Add.

Hope this helps you.

I think Oneavenue's method won't work. Bind does NOT add slave zones to the secondary DNS server, you need to add them manually by editing named.conf. Or write a script that does it for you. We run a mix of DA, cpanel and no-cp servers using a primary nameserver on a DA server and a secondary nameserver on a cpanel server.