Deploy a chain of DNS servers for a zone.
For example, you have a master DNS server on a provider’s premises, a slave server in your DMZ connected to Internet, and you want another slave 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 Master DNS role to server A.
- In same zone, assign a Slave role to server B and then specify server A as a source of zone transfers.
- In same zone assign a Slave role to server C and then specify server B as a source of zone transfers.
- Deploy this configuration to three managed Windows servers in the Read-Write mode. Servers A and B deploy and work well, but on server C the zone appears in the not loaded condition, showing that it is not working.
This condition arises from the current rules of Slave deployment. Address Manager adds Allow Transfer and Also Notify options into the deployment XML for a Master server, but it does not add them for a Slave server.