Deploy a chain of DNS servers for a zone.
For example, you have a primary DNS server on a provider’s premises, a secondary server in your DMZ connected to Internet, and you want another secondary server in your productive network. This server receives zone transfers from the server in the DMZ (not from the provider).
To deploy a chain of servers:
- Create a zone called example.com, and then assign a primary DNS role to server A.
- In same zone, assign a secondary role to server B and then specify server A as a source of zone transfers.
- In same zone assign a secondary role to server C and then specify server B as a source of zone transfers.
Deploy this configuration to managed BlueCat servers in the Read-Write
Note: To deploy a chain of servers for a zone, Address Manager adds the Allow Transfer and Also Notify options into the deployment XML for a primary server but it doesn't add them for a secondary server.
This condition arises from the current rules of secondary deployment. Address Manager adds Allow Transfer and Also Notify options into the deployment XML for a primary server, but it does not add them for a secondary server.