Dns problems

[liam]

Hi y'all

I have a windows 2000 domian, running advanced server with
2 DNS servers with Active Directory Integrated Zones.
Both DNS servers are listening for requests.
I have member servers which are configured for Primary and
Secondary DNS IP's.
If one DNS goes down, then failover to the other will
occur. I see a problem in this that there seems to be a
delay in response before the active DNS starts to reply to
requests.
Question:
Is there a way/ a setting to shorten the delay so that ALL
servers query the Active DNS server.

Please help

 

[tash]

Mate sounds like those so called MVP's are unable to
answer this question. They're not that hot
Wish I could help though but I gon't know maybe something
to do with TTL's though

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Mate sounds like those so called MVP's are unable to
answer this question. They're not that hot
Wish I could help though but I gon't know maybe something
to do with TTL's though

Nothing to do with TTL's and I answered his question in his other thread.
"Is there no one who can answer this?"

 

[Ace Fekay [MVP]]

In

Hi y'all

I have a windows 2000 domian, running advanced server with
2 DNS servers with Active Directory Integrated Zones.
Both DNS servers are listening for requests.
I have member servers which are configured for Primary and
Secondary DNS IP's.
If one DNS goes down, then failover to the other will
occur. I see a problem in this that there seems to be a
delay in response before the active DNS starts to reply to
requests.
Question:
Is there a way/ a setting to shorten the delay so that ALL
servers query the Active DNS server.

Please help

I guess 3 times a charm.

This has to do with the failover time out because of the way the DNS
resolver service works. Herb already responded to you about that in your
other post. You can switch the second for the first if you feel the first
DNS is not a reliable server. Read the 3rd link below, which includes
registry settable time out settings but you will not see a noticable
difference.

Here's info on how it works:

DNS Client Query - Microsoft Windows 2000 Server Documentation:
http://www.microsoft.com/windows200...00/en/server/help/sag_DNS_und_HowDnsWorks.htm

Querying DNS Servers - how the resolver service works:
http://www.microsoft.com/technet/tr...prodtechnol/winxppro/reskit/prjj_ipa_bsmz.asp

Windows 2000 DNS Client Side Resolver Service [includes resolver eligibility
(what DNS is being considered to use), subnet priortization, round robin,
cache etc]:
http://www.microsoft.com/windows2000/techinfo/reskit/samplechapters/cncf/cncf_imp_miqe.asp

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroup so all
can benefit. This posting is provided "AS-IS" with no warranties and
confers no rights.

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

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================

 

[Ace Fekay [MVP]]

In Ace Fekay [MVP] in
<PleaseSubstituteMyActualFirstName&[email protected]> posted their
thoughts, then I offered mine

Just to add, if you feel that your DNS servers are not reliable enough to
handle the infrastructure's requirements and need to make sure that failover
will handle it, as I said, due to your lack of confidence in the machine,
the I would change the first entry to a reliable DNS server or upgrade the
hardware and make the second entry the unreliable one, which would be in
this case, reliable enough to handle the failover until you resolve the
issue.

DNS failovers rarely occur, but when they do, there will be a certain amount
lag time for the DNS client side resolver to perform its function of
checking the first entry first and go thru its girations until it concludes
that its no longer viable and yanks it out of the eligible resolvers lists
so it can go on to the second one.


Ace