A. Only one primary version of the DNS zone should exist for zones that aren't Active Directory-integrated. If necessary, you can create additional secondary versions of zones on other DNS servers to support fault tolerance and load balancing.
If you have multiple primary versions of a zone that isn't Active Directory-integrated, those zones won't replicate or remain synchronized. Here are the possible actions that can occur when you move these multiple versions into Active Directory (AD) for storage:
- After the first DNS server stores its zone information in AD, all subsequent DNS servers lose their DNS zone content and use the first DNS server's zone information in AD.
- As each DNS server is modified to store its information in AD, the new DNS zone data overwrites the existing DNS zone data in AD.
- As each DNS server is modified to store its information in AD, the new DNS server's data merges with the existing data.
When you opt to integrate the second instance of the zone (or any subsequent instance of the zone on a different DNS server) in AD--as explained in the FAQ "How can I change how DNS information is stored on a DNS server?" (http://www.winnetmag.com/articles/index.cfm?articleid=43104)--you can choose between the first and second options. In the Active Directory Service box, which the figure at Figure shows, you must select either "Discard the new zone, and load the existing zone from Active Directory" or "Overwrite the existing zone in Active Directory with the new zone." After you make your selection, click OK, then click OK again to confirm it.