<div>
Not sure why it's acting that way, but you might try setting up a stub zone for asdf.com instead of using the conditional forwarders.
</div>


Not sure why it's acting that way, but you might try setting up a stub zone for asdf.com instead of using the conditional forwarders.

<div>
<div class="content wysiwyg-content">
Server A (2008r2) has a VPN to asdf.com, and has a conditional fwd setup with 2 DNS servers living on the asdf.com domain<br />
Server B (2012) has a VPN to SiteA, and the same cond. fwds.<br />
<br />
It seems as though if server A looses its VPN connection, which means no route to the cond. fwd DNS server then server B wont use the cond. fwd unless I restart DNS services. &nbsp;So when the 2012 box cant get to the cond. fwd DNS server to resolve asdf.com, it uses it's regular DNS services - and then resolves to the wrong IP, breaking an application. &nbsp;It will keep resolving incorrectly until I restart dns services, then flushdns on all workstations so they resolve correctly.<br />
Seems as though server A on 2008r2 figures it out and starts using the cond. fwd again, no need to restart.<br />
<br />
Anyone know how this works or what to change? &nbsp;I saw a timeout setting on the cond. fwd, it was set to 3 sec which seemed short, changed it to 30 seconds. &nbsp;But honestly I NEVER want the DNS server to use the &quot;backup&quot; DNS settings, as that resolves asdf.com to a public IP which breaks the application.
</div>
</div>


Server A (2008r2) has a VPN to asdf.com, and has a conditional fwd setup with 2 DNS servers living on the asdf.com domain
Server B (2012) has a VPN to SiteA, and the same cond. fwds.

It seems as though if server A looses its VPN connection, which means no route to the cond. fwd DNS server then server B wont use the cond. fwd unless I restart DNS services.  So when the 2012 box cant get to the cond. fwd DNS server to resolve asdf.com, it uses it's regular DNS services - and then resolves to the wrong IP, breaking an application.  It will keep resolving incorrectly until I restart dns services, then flushdns on all workstations so they resolve correctly.
Seems as though server A on 2008r2 figures it out and starts using the cond. fwd again, no need to restart.

Anyone know how this works or what to change?  I saw a timeout setting on the cond. fwd, it was set to 3 sec which seemed short, changed it to 30 seconds.  But honestly I NEVER want the DNS server to use the "backup" DNS settings, as that resolves asdf.com to a public IP which breaks the application.

Server 2012 DNS with conditional forwarders

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

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.