Afficher un message
Vieux 27/03/2006, 19h28   #2
Herb Martin
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: DNS & DHCP on multiple Win2003 Servers

"Degen Ende" <degen.ende@gmail.com> wrote in message
news:1143484489.951215.222390@v46g2000cwv.googlegr oups.com...
> Currently, I have a single Windows 2000 Advanced Server running DNS and
> DHCP for my corporate domain.
>
> I'm going to replace that with 2 Windows 2003 Enterprise Servers.
>
> DNS1 will be my primary DNS/DHCP server.
> DNS2 will be my secondary DNS/DHCP server.
>
> In terms of DNS, this is fairly simple. Set DNS1 as the primary and
> DNS2 as the secondary, configure for zone transfer, etc.



> In terms of DHCP, I don't know the best way to handle any kind of
> failover. As I understand it, Network Load Balancing (NLB) is out
> because of how NLB works. Is it possible to use Cluster Services (MSCS)
> instead for DHCP?


Whenever we hear someone is going to "replace" such servers,
many of us strongly urge you UPGRADE instead and keep it
simple.

> To make matters MORE interesting, a few months down the line we're
> going to put in a third DNS server at an offsite location (I can't
> explain why, my head hurts). Will this cause a problem?


There is no reason it should cause any problems.

> Would I have to
> come up with an NLB/MSCS for my DNS which may conflict with my DHCP
> failover scenario?


Normally DNS is NOT setup to use NLB or Clustering
since DNS servers mostly do that based on the way clients
use the DNS.

DHCP does NOT deal well with NLB either; it really needs
clustering.

Since clustering is on a PER APPLICATION basis (unlike
NLB which is per node) this works out even if DNS is on
the same box with the DHCP server.

> Any would be outstanding. Thank you in advance.



Is Active Directory involved in any of this?

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


  Réponse avec citation
 
Page generated in 0,17308 seconds with 9 queries