Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 305
  • Last Modified:

Secondary DNS server was not being asked for requests

We have two DNS servers - DNS1 and DNS2.  Our primary DNS server went down over the weekend and our secondary server must not have been being servicing requests.  Shouldn't the client try the secondary DNS if it cannot reach the primary?
0
scottvin
Asked:
scottvin
1 Solution
 
grsteedCommented:
Yes if both are configured on the client.  Ipconfig /all will tell you.   If you're using DHCP it will be whatever the server is handing out for DNS.

Cheers,
Gary
0
 
scottvinAuthor Commented:
They are both configured on the client.  However, they were not asking the secondary for requests.  What is the timeout for DNS requests?
0
 
grsteedCommented:
Not sure what the timeout is exactly but I think it's a matter of seconds.

Basically if it doesn't get a response from the preferred DNS server (the first on in the list) it will (should?) try the next one.

I just did a test on my PC (XP Pro) with Ethereal and it goes back and for with the DNS requests using one for a while and then the other.

Was the primary down hard?

Can you force your PC to use the secondary to see if it's responding? Try this

go to the  command prompt and enter NSLOOKUP.

enter SERVER w.x.y.z  (your secondary DNS)

then enter www.google.com  and see if you get the proper response.

Cheers,

Gary
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
scottvinAuthor Commented:
Non-authoritative answer:
Name:    www.l.google.com
Addresses:  66.102.7.99, 66.102.7.104, 66.102.7.147
Aliases:  www.google.com

Worked fine.  Yes my primary was down hard.
0
 
grsteedCommented:
hmmm,  not sure what to tell you.  And since it's not happening now (the primary is back up right?) There's not much else to do.

Maybe  someone else will chime in.

Cheers,
Gary
0
 
scottvinAuthor Commented:
Yeah - It's back up.  Now I am hearing that is wasn't everyone.  I am going to have those particular users IP setting emailed to me.  Will let you know what I find.
0
 
mjdealeCommented:
Try to Ping The secondary DNS sever from the client and see if you can ping. if you can Ping it than reboot the DNS server or the service and should work fine. if not than it's a hardware failure.

Mehdi,
0
 
grsteedCommented:
Mehdi,

He was able to query and get a response from the secondary using nslookup as shown above so I think it's fine.

Cheers,
Gary
0
 
Robin888Commented:
Hi scott,

I would suggest isolate and troubleshoot on the problem client computers. something might be blocking on the client computers.. try ipconfig /flushdns on those computers, ipconfig /release/renew, see if those command works. I agree with gary, the speed should be seconds switching from primary dns to secondary dns....
Try check event viewer on those problem client computers.
hmm maybe you have the problem isolated computers on different network?

R
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now