i have a network with two 2008r2 domain controllers. DNS is running on each, and they each point to each other as primary DNS, and themselves as secondary. This morning i noticed that after running updates on the 'secondary' DC/DNS and rebooting it, while it was rebooting, outlook struggled to find the exchange server for a couple of users authenticated against that server. it connected finally in one instance (because i think the dc had rebooted) and in another prompted the user with the login dialog.
If the logonserver becomes unavailable, (these users are already authenticated and browsing the network) does outlook not fall back on dns to resolve the address? It seemed to me that redundant dns should eliminate that kind of behaviour, the primary dns server was still online? Is it tied to the logonserver, or perhaps something is configured incorrectly? What should i expect under these circumstances? How does outlook resolve exchange if the logonserver becomes unavailable after they have authenticated.