We have a client who wants us to manage their laptops, running our custom application, through a site-to-site VPN tunnel. We will create a DNS zone hem for them in our internal DNS with some of their servers. One of their servers is machineA.companyB.com, and another is machineB.northamerica.companyB.com. Their domain is northamerica.companyB.com. After creating the second one in Microsoft DNS as a host record DNS automatically created a subzone, northamerica, and placed machineB in it. My problem is this. I went to create a host record in companyB.com called "northamerica" and assign it the IP address of one of their domain controllers. Microsoft DNS told me the host record was successfully created but I can
not see it. The goal was to make "northamerica.companyB.com" resolve to a DC so when joining the northamerica.companyB.com domain the managed laptop will find the DC. So I have two questions. One, is this the recommended way to setup DNS so a laptop can find a DC for a different domain over a site-to-site VPN tunnel? Two, if it is, how do I overcome the apparent inability to creat a host record called "northamerica.companyB.com" if a subzone "northamerica" exists?