DNS client failover

  • Thread starter Thread starter Frank Dahlman
  • Start date Start date
F

Frank Dahlman

I have 2 DNS servers running active direcroty integrated
zones for our domain. When I have to bounce our dns
server that is listed in dhcp as our primary DNS server,
the clients lose their ability to get to e-mail and other
network resources for a while. Usually a couple minutes.
How long should a client take to go from it's primary dns
server to its secondary dns server?
 
AF> It will usually go to the next entry when the first
AF> gives with an NXDOMAIN response or no response.

No. It will not query the alternate server if the preferred server provides
an answer. "No such name" is an answer.
 
In
Frank Dahlman said:
I have 2 DNS servers running active direcroty integrated
zones for our domain. When I have to bounce our dns
server that is listed in dhcp as our primary DNS server,
the clients lose their ability to get to e-mail and other
network resources for a while. Usually a couple minutes.
How long should a client take to go from it's primary dns
server to its secondary dns server?

Usually right away. It will usually go to the next entry when the first
gives with an NXDOMAIN response or no response. If the second entry doesn't
have the records, which we usually see if they are an ISP's, but doesn't
seem to be the case here, it will fail as you are describing. Unusual that
the second entry, being AD Integrated, would give you this error.

Curious, why are you bouncing the DNS server? Any errors in the Event logs?
If so, can you post the Event ID #'s? I have 3 servers here working like
clockwork and haven't been downed unless I had to install a patch or service
pack or something that required a reboot.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Jonathan de Boyne Pollard said:
No. It will not query the alternate server if the preferred server
provides an answer. "No such name" is an answer.

Got me there. You're right and I forgot about that. A no answer response is
a response and will stop there without going to the next one.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Frank Dahlman said:
bounce it. Then the big boss man put a third party app on
there when it had to be bounced again. So both times it
gave a delay. I found no errors on the clients or the
server.

Well, then I would say that it should fail over after "NOT" getting a
response from the first entry. Maybe it's already at the second entry. If
that is the case, then it will NOT go back to the first entry unless the
machine or just the DNS client service is restarted.

But not sure why you would want to bounce the server during production hours
to be installing applications on a needed server running a critical service
such as DNS?

And as for the boss, (if he reads this), with all due respect, him running a
business should know when and not when to bounce a server. Wouldn't you say
that ensuring available services ensures productivity? Let's do this after
hours.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top