Exchange domain request caching - Wont use other DC's when the primary goes down

Hi folks, So in my clients environment they have multiple Domain Controllers, but whenever a DC goes down Exchange keeps sending requests to that DC instead of using the other available ones, and this process doesnt time out for at least 12 hours, after said 12 hours it decides to use to another DC.

Is there any way to speed up this process or force Exchange to use the other DC?

Thanks in advance.
Raymond BrooksAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AmitIT ArchitectCommented:
Check NIC DNS setting.  Looks like DNS is not configured properly.
0
Will SzymkowskiSenior Solution ArchitectCommented:
This is definetly not the outcome that should be happening if everything is working properly with your Active Directory environment. The correct outcome is when a primary DNS server is no longer reachable within 1 second on the network, it will use the next DNS IP address for the query (secondary IP address).

On your exchange server you need the following...
- Primary and Secondary DNS entires (both DNS servers need to be in the same AD Site, where Exchange resides)
- Both domain controllers need to be DC/DNS/GC

Make sure that you check your Active Directory Health and Replication using the following commands..

repadmin /replsum
repadmin /showrepl
repadmin /bridgeheads
DCDiag /v

If everything is correct there has been a known issue with Microsoft DNS called DNS sticky Keys. This is a syndrom when DNS will not release from the primary. This is not normal behavior and it should fail over to secondary just after 1 second of not being available.

Will.
0
Amit KumarCommented:
By Default, Exchange checks for the available DC’s every 15 mins. In case any DC is rebooted/down, next time when exchange does the query, it identifies that DC which is not reachable and will mark it as down. After which, Exchange will try using another available DC.

If Exchange doesn’t gets a response from a DC, it will not switch to another DC immediately. Only when it thinks that the DC is not functional, it switches to another DC. Till that time, it will continue to send the requests to the DC which isn’t responding also.

Check few things:

1. Primary and Alternative DNS should be there to respond on Exchange server.
2. All DCs should have its IP as primary DNS, even it can create such issue.

However, we have same issue on few Exchange servers in our environment. I have already logged a case in MS and working with them. In last reboot activity of DC we have capture Pref logs, Net Mon logs and Event viewer logs those are given to MS for analysis. but still waiting for reply.
0
AmitIT ArchitectCommented:
I want you to also check, if someone hardcoded DC's for this Exchange server. There is a command in Exchange, where you can set it contact preferred DC. If that is the case, you might need to change it. Ref:
https://marckean.wordpress.com/2011/06/30/exchange-2010-domain-controller-and-global-catalog-servers-being-used-by-exchange/

As you haven't mentioned Exchange version, I have it for 2010.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Raymond BrooksAuthor Commented:
Thanks, just yesterday i was going over some documentation on DAC and saw the Preferred AD command.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.