How to configure a secondary zone as a primary.
You may want to configure a DNS server hosting a secondary copy of a zone to be the primary for another secondary server. For example, Server1 (located in North America) hosts the primary copy of the example.com zone. Server2 and Server3, (located in Europe) host secondary copies of the zone.
While it is not uncommon to configure both European servers to request zone transfers from the single primary, configuring Server2 to be the primary for Server3 can save bandwidth because the distance between the two European servers is much less than the distance between Server1 and Server3.
- Add the IP address of the secondary acting as primary in the Zone Transfer interface
- Add the Allow Zone Transfer deployment option to the secondary acting as a primary.
- Add the Notify and Notify Additional Servers deployment options to the
secondary acting as a primary.Note: Address Manager is not able to import this configuration. After importing the zone data from all three servers, you must configure the Zone Transfer interface in Address Manager.
To configure the zone transfer interface:
- Navigate to the IP block, IP network, view, or zone for which you want to add the Secondary Deployment Role.
- Click the Deployment Roles tab.
- Click New, and then select DNS Role. The Add DNS Role page appears.
- From the Type drop-down menu select Slave.
- Under Server Interface, click Select Server Interface. The Select Server Interface page appears.
- Click the server name, and then select the option for the server interface you want to use.
- Click Add.
- Under Zone Transfers, click Select Server Interface. The Select Server Interface page opens.
- Click the name of the server that should hold the primary role, and then select the option for the server interface you want to use.
- Click Add.
- Click Add at the bottom of the page.