Re: GC & DNS ISSUE


"Danny Sanders" <DSanders@xxxxxxxxxxxxxxx> wrote in message
news:uQkHA20hHHA.4520@xxxxxxxxxxxxxxxxxxxxxxx
I'm talking about just the 1 AD integrated DNS zone. Each DNS server
listed on the client are participating in the AD integrated DNS.

No of zones is irrelevant -- clients are using a DNS server (set) to find
all zones.

Participating is NOT even DIRECTLY required. All that is required is
that every DNS server listed (as preferred OR alternate) be able to
resolve every name the users will ever need.

Take the "preferred" DNS server down and the client does not seem to roll
over to the "alternate".

Put the alternate as preferred on the client and things work as expected.
I've tested with Win 2k SP 4 servers and Win 2k and XP clients and Win 2k3
servers with Win 2k and XP clients, the "roll over" never seems to happen.

DDS

"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:%23r9HSyzhHHA.4676@xxxxxxxxxxxxxxxxxxxxxxx

"Danny Sanders" <DSanders@xxxxxxxxxxxxxxx> wrote in message
news:eLSFj$rhHHA.392@xxxxxxxxxxxxxxxxxxxxxxx
Let's recommend he do it slightly differently: Set all of the DNS
clients,
including the DCs, to use BOTH of the the DNC-DCs so that when
one is down the fail over is automatic.
Have you actually gotten this to work? Because I haven't.

Of course -- this is the normal way that most everyone does it.

Unless of course we have somehow miscommunicated and you are
talking about something else.

Each of the internal DNS servers SHOULD be in the DNC Client
properties as Preferred with Alternate(s) until you have 2-5 or
so at least.

All DNS servers listed must however return the EXACT SAME
set of answers. You cannot have one server return some zones and
expect another server to return others.

I was hoping it would work this way but I haven't had any luck getting
it to work that way.
Not on a Win 2k domain or a Win 2k3 domain w/ Win 2k Sp 4 and XP SP 2
clients.

What's the secret?

What's you problem when you try it?


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)





.

Relevant Pages

  • Re: Vista clients became unresponsive after network move
    ... used, and all clients are static and incorrectly configured, I can ... network connection. ... reverse zone. ... DNS server events since the move: ...
    (microsoft.public.windows.server.networking)
  • Re: Vista clients became unresponsive after network move
    ... If DHCP is not being used, and all clients are static and incorrectly configured, I can ... network connection. ... reverse zone. ... DNS server events since the move: ...
    (microsoft.public.windows.server.networking)
  • Re: Vista clients became unresponsive after network move
    ... being used, and all clients are static and incorrectly configured, I can ... network connection. ... reverse zone. ... 11/5 - DNS server has started ...
    (microsoft.public.windows.server.networking)
  • Re: Vista clients became unresponsive after network move
    ... If DHCP is not being used, and all clients are static and incorrectly configured, I can understand the problems. ... network connection. ... reverse zone. ... 11/5 - DNS server has started ...
    (microsoft.public.windows.server.networking)
  • Re: AD clients can no longer connect to DC in 2003
    ... perhaps you should look at the clients. ... Verify that the clients are pointing to an existing, internal DNS server ... However it does not prove that the correct SRV records are present. ... >net start netlogin>>That should get logins going again. ...
    (microsoft.public.windows.server.active_directory)
Quantcast