<div>
I'm wondering whether using a secondary forward lookup zone for the remote domain would suffice? Surely if my DC holds a DNS zone for the domain then resolution should work?
</div>


I'm wondering whether using a secondary forward lookup zone for the remote domain would suffice? Surely if my DC holds a DNS zone for the domain then resolution should work?

<div>
Fair enough, that answers that!
</div>


<div>
<div class="content wysiwyg-content">
I have 2 x Server 2008 R2 DC's configured with a single domain, we acquired another company and now have a trust in place with that domain.<br />
<br />
The trust works well and we have conditional forwarders in place for DNS resolution between the trust. However, I'm currently unable to query DNS without specifying FQDN that belongs in the remote domain.<br />
<br />
For example:-<br />
<br />
LOCAL-SERVER lives in domain 1, REMOTE-SERVER lives in domain 2. In order to query REMOTE-SERVER from domain 1 I have to specify the FQDN of REMOTE-SERVER. DNS queries time out unless I specify FQDN. I was of the understanding that if DNS cannot resolve name using primary DNS then a recursive query would be sent across forwarders until it resolved the name?<br />
<br />
The only way I can get this to work is to specify DNS suffixes in NIC adapter in order. For example, suffic1.local, suffix2.local etc. To me this does not seem like the correct way to configure DNS.<br />
<br />
I have tried using forwarders but no joy. Any thoughts?
</div>
</div>


I have 2 x Server 2008 R2 DC's configured with a single domain, we acquired another company and now have a trust in place with that domain.

The trust works well and we have conditional forwarders in place for DNS resolution between the trust. However, I'm currently unable to query DNS without specifying FQDN that belongs in the remote domain.

For example:-

LOCAL-SERVER lives in domain 1, REMOTE-SERVER lives in domain 2. In order to query REMOTE-SERVER from domain 1 I have to specify the FQDN of REMOTE-SERVER. DNS queries time out unless I specify FQDN. I was of the understanding that if DNS cannot resolve name using primary DNS then a recursive query would be sent across forwarders until it resolved the name?

The only way I can get this to work is to specify DNS suffixes in NIC adapter in order. For example, suffic1.local, suffix2.local etc. To me this does not seem like the correct way to configure DNS.

I have tried using forwarders but no joy. Any thoughts?

Trust DNS Resolution for Unqualified Names

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.