The "Alternate DNS Server" is actually never put into work ??

I shut down one of DNS servers for a couple of hours for maintenance and this DNS happens to be listed as "Preferred DNS Server" on all computers. After I shut down, my LAN started to be disconnected simply because this "Preferred DNS Server" is temporarily down. BUT don't forget we do have another secondary DNS server properly set up as "Alternate DNS Server". How come this "Alternate DNS Server" was NOT coming to help when the Preferred DNS Server is down??
Did I miss anything so the Alternate DNS Server never comes to play its role? Please help.
CastlewoodAsked:
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.

Nick RhodeIT DirectorCommented:
And DHCP is pushing both DNS servers correct?  Are the two servers not syncing properly? Perhaps DNS service is not started on the 2nd server?
CastlewoodAuthor Commented:
DHCP should not be a factor since computers with static assigned IP are with the issue too.
I verified and confirmed that both DNS servers are working well individually. The issue here is, the "Alternative DNS Server" is just not playing its role to kick in when the Preferred is down.

But don't you guys have this identical issue at your environment?
MaheshArchitectCommented:
What exactly happens when you say LAN computers started disconnection ?
Are the disconnected server also holding Active Directory and FSMO role ?

Internet gone down ?
may be DNS forwarder is set on disconnected DNS server
OR
Applications are stopped working ?
 
Mahesh
piwowarcCommented:
Hello

Are you able to query both those servers with success?  If you don't have / cant use DIG, simple nslokup can force query. nslookup RECORD SERVER (ex nslookup yahoo.com 8.8.8.8).

Windows resolver (dns client) is an aggressive fella and tries to query alternate dns after 1s of not getting answer from primary one and in couple of seconds it will bomb all of them (if you have more than 2 configured) so in real life you may have some queries going to alternate server anyway without knowing it.

Focus on ensuring you can reach backup DNS and it operates properly. And if you suffer WAN outage to check DNS is alive, ask something hosted locally obviously (like internal records) so you know server actually responds, it may just have problems reaching internet for answer.

Regards

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
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
DNS

From novice to tech pro — start learning today.