You are a network administrator for Alpine Ski House.The network consists of a single Active Directory domain named alpineskihouse.com.

Your company acquires a company named Adventure Works.The Adventure Works network consists of a single Active Directory domain named adventure-works.com.

A server named Server32 is a network-management application server in the adventure-works.com domain. Server32 accesses all of the desktop client computers to perform automated software upgrades and hardware inventory. The network-management software on Server32 references desktop computers by unqualified host names, which are resolved to clientname.adventure-works.com by using a DNS server.

You join Server32 to your domain to become server32.alpineskihouse.com. The Server32 IP address is 10.10.90.90

You are gradually migrating all adventure-works.com desktop client computers to your domain to become clientname.alpineskihouse.com.You do not have access to the adventure-works.com DNS server.When Server32 attempts to apply an update to the client computers, the network-management software returns many alerts that say that desktop computers cannot be found.

You want to allow the network-management software on Server32 to resolve unqualified client computer host names in adventure-works.com or alpineskihouse.com, and you want to use the minimum amount of administrative effort.

What should you do?

A.
On the DNS server for alpineskihouse.com, add a zone for adventure-works.com.Create a host (A) record for server32.adventure-works.com that points to 10.10.10.90.

B.
On Server32, in System Properties, type adventure-works.com in the Primary DNS suffix of this computer field in the DNS Suffix and Netbios Computer Name setting.

C.
On Server32, configure a Hosts file that contains the name and IP address of every network computer.

D.
On Server32, in Advanced TCP/IP Settings, add adventure-works.com and alpineskihouse.com to the Append these DNS suffixes (in order) setting.