Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


DNS Failover on Windows Clients

Posted on 2014-09-10
Medium Priority
Last Modified: 2015-06-27

We've got multiple domain controllers based at our head office all running AD DS & DNS.

Our Primary domain controller is configured to be the Primary DNS server for our Windows servers and workstations. Recently our primary controller has gone down twice and although we're making our AD infrastructure more resilient can anybody explain why workstations and servers are not failing over to the secondary DNS server specified in their NIC? It appears that they carry on querying the primary DNS server continually despite it not being available

Question by:Jack Lloyd
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
LVL 19

Expert Comment

by:Miguel Angel Perez Muñoz
ID: 40314111
DNS resolution first do on primary and secondary if first fails. This causes some lag in case of primary is down (until timeout is reached and query is send to secondary) but DNS must be resolved.
Could you check your computers can reach to secondary DNS and do querys? (you can test using nslookup).

Author Comment

by:Jack Lloyd
ID: 40314118
Yes they can reach the secondary DNS server and perform DNS look ups. It just doesn't fail over when there's an issue with the main domain controller.

Is there some sort of time out we can set so it can flip onto the secondary domain controller much faster?


LVL 19

Expert Comment

by:Miguel Angel Perez Muñoz
ID: 40314131
Timeout is one second:

Are you sure is DNS related problem?

Accepted Solution

Jack Lloyd earned 0 total points
ID: 40356887

We figured this out in the end, turns out both the servers had been rebooted at the exact same time with some patch management software. One (the  primary) didn't come up cleanly but was still accepting DNS queries, therefore not failing over to the next server.

Thanks for your help though guys.

LVL 35

Expert Comment

by:Seth Simmons
ID: 40854370
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to set-up an On Demand, IPSec, Site to SIte, VPN from a Draytek Vigor Router to a Cyberoam UTM Appliance. A concise guide to the settings required on both devices
A procedure for exporting installed hotfix details of remote computers using powershell
Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question