You are the network administrator for I-Technic Industries. The network contains Windows XP Professional and Windows Server 2003 computers. You have two Windows 2003 domain controllers named DC1 and DC2 that are responsible for a single domain named itechind.com. Your primary DNS server is installed on a domain controller named DC1.itechind.com. You have one secondary DNS server installed on a member server named Srv2.itechind.com. You want to ensure that updates can be made to any server. You also want to optimize and simplify the management of DNS replications and zone transfers. What should you do?
A. Promote Srv2.itechind.com to a domain controller. B. On DC1.itechind.com, add Srv2.itechind.com to the notify list. C. On DC1.itechind.com, set the Time to Live (TTL) value in the SOA record to a higher value. D. Remove the DNS Server service from Srv2.itechind.com. Install the DNS Server service on DC2.itechind.com. Convert the zone hosted by DC1.itechind.com to an Active Directory-integrated zone.
Remove the dns server service from srv2.itechind.com. install the dns server service on dc2.itechind.com. convert the zone hosted by dc1.itechind.com to an active directory-integrated zone.-explanation: you should remove the dns server service from srv2.itechind.com. next you should install the dns server service on dc2.itechind.com. finally, you should convert the zone hosted by dc1.itechind.com to an active directory-integrated zone. converting the zone hosted by dc1.itechind.com to an active directory-integrated zone ensures that updates can be made to any server. in addition, using this zone type, zone transfers occur automatically as part of active directory replication. you should not promote srv2.itechind.com to a domain controller. you already have another domain controller that is used as part of your dns structure. this solution does not change the zone type, which is necessary to achieve your goals. you should not add srv2.itechind.com to the notify list on dc1.itechind.com. this only ensures that dc1.itechind.com contacts srv2.itechind.com when changes are made to the dns database. it does not change the zone type, which is necessary to achieve your goals. you should not set the time to live (ttl) value in the start of authority (soa) record on dc1.itechind.com to a higher value. this setting only affects the amount of time a server can cache information for a zone.