new w2k3 2ndary (member) + existing w2k primary (DC) = problem?
- From: "mikeindo" <mikeindo@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 29 Jun 2005 14:00:01 -0700
I'm setting up W2K3 as a secondary DNS server in our office. A W2K Server is
already the primary. It's a primary zone. While we do have a Linux box, I'm
not going to join it to the domain, so shouldnt I be safe to change to
AD-integrated? (I like the whole 'secure updates' thing.) The thing is, the
W2K3 Server is only a member server, not a DC (yet). Is that a problem?
Will it still replicate?
.
- Follow-Ups:
- Re: new w2k3 2ndary (member) + existing w2k primary (DC) = problem?
- From: Herb Martin
- Re: new w2k3 2ndary (member) + existing w2k primary (DC) = problem?
- From: Todd J Heron
- Re: new w2k3 2ndary (member) + existing w2k primary (DC) = problem?
- Prev by Date: Re: DNS Poisoning, pharming, pollution
- Next by Date: Re: 4 to 10 minute login times for XP PRO machines only
- Previous by thread: Slow internet connection with Server 2003
- Next by thread: Re: new w2k3 2ndary (member) + existing w2k primary (DC) = problem?
- Index(es):
Relevant Pages
|