|
|
For various reasons, we ended up with a primary/secondary DNS setup using two
Windows 2000 servers on our AD 2003 Domain.
What is the cleanest, most direct way to migrate our DNS setup to an
AD-integrated setup...just add new 2003 AD-integrated DNS servers and migrate
the clients to them?
Thanks!
|
|
|
[Quoted Text] > What is the cleanest, most direct way to migrate our DNS setup to an
> AD-integrated setup...
See:
http://support.microsoft.com/kb/198437
>just add new 2003 AD-integrated DNS servers and migrate
> the clients to them?
Not following you here. Are you removing the original Win 2k DNS servers?
hth
DDS
"Chris U" <Chris U[ at ]discussions.microsoft.com> wrote in message
news:0921D578-EF9B-4E2B-BA8C-C0F0A423BA47[ at ]microsoft.com...
> For various reasons, we ended up with a primary/secondary DNS setup using
> two
> Windows 2000 servers on our AD 2003 Domain.
>
> What is the cleanest, most direct way to migrate our DNS setup to an
> AD-integrated setup...just add new 2003 AD-integrated DNS servers and
> migrate
> the clients to them?
>
> Thanks!
|
|
AD Integrated isn't an option on the Change Zone Type on the 2000 DNS
servers, so I figured we would need to bring up 2003 servers w/DNS to make
this change.
I want to remove one server (old hardware) but am open to keeping the other
online if there's a way to Change it.
Thanks for the input!
"Danny Sanders" wrote:
[Quoted Text] > > What is the cleanest, most direct way to migrate our DNS setup to an > > AD-integrated setup... > > > See: > http://support.microsoft.com/kb/198437> > > >just add new 2003 AD-integrated DNS servers and migrate > > the clients to them? > > Not following you here. Are you removing the original Win 2k DNS servers? > > > hth > DDS > > > "Chris U" <Chris U[ at ]discussions.microsoft.com> wrote in message > news:0921D578-EF9B-4E2B-BA8C-C0F0A423BA47[ at ]microsoft.com... > > For various reasons, we ended up with a primary/secondary DNS setup using > > two > > Windows 2000 servers on our AD 2003 Domain. > > > > What is the cleanest, most direct way to migrate our DNS setup to an > > AD-integrated setup...just add new 2003 AD-integrated DNS servers and > > migrate > > the clients to them? > > > > Thanks! > > > |
|
|
[Quoted Text] > AD Integrated isn't an option on the Change Zone Type on the 2000 DNS
> servers, so I figured we would need to bring up 2003 servers w/DNS to make
> this change.
Sounds like the Win 2k DNS servers are not domain controllers? AD integrated
DNS allows the DNS information to replicate along with the Active directory
information, no special replication just for DNS like the primary/secondary
model. Active Directory information is ONLY replicated to domain controllers
and as a result AD integrated DNS is only available on a domain controller
housing DNS.
Suggest you promote the Win 2k server, the one you want to keep, to a domain
controller. Set the DNS zone as AD integrated. Add the Win 2k3 server to the
domain (you may have to run adprep if this is the first Win 2k3 server in
the domain) and promote to a DC and the DNS info will replicate to the new
Win 2k3 server.
Done.
Now you have 2 AD integrated DNS servers and a Win 2k server on old hardware
that you can do with what you want.
hth
DDS
"Chris U" <ChrisU[ at ]discussions.microsoft.com> wrote in message
news:2148676B-66E9-4289-8031-B369B3761A5C[ at ]microsoft.com...
> AD Integrated isn't an option on the Change Zone Type on the 2000 DNS
> servers, so I figured we would need to bring up 2003 servers w/DNS to make
> this change.
>
> I want to remove one server (old hardware) but am open to keeping the
> other
> online if there's a way to Change it.
>
> Thanks for the input!
>
> "Danny Sanders" wrote:
>
>> > What is the cleanest, most direct way to migrate our DNS setup to an
>> > AD-integrated setup...
>>
>>
>> See:
>> http://support.microsoft.com/kb/198437
>>
>>
>> >just add new 2003 AD-integrated DNS servers and migrate
>> > the clients to them?
>>
>> Not following you here. Are you removing the original Win 2k DNS servers?
>>
>>
>> hth
>> DDS
>>
>>
>> "Chris U" <Chris U[ at ]discussions.microsoft.com> wrote in message
>> news:0921D578-EF9B-4E2B-BA8C-C0F0A423BA47[ at ]microsoft.com...
>> > For various reasons, we ended up with a primary/secondary DNS setup
>> > using
>> > two
>> > Windows 2000 servers on our AD 2003 Domain.
>> >
>> > What is the cleanest, most direct way to migrate our DNS setup to an
>> > AD-integrated setup...just add new 2003 AD-integrated DNS servers and
>> > migrate
>> > the clients to them?
>> >
>> > Thanks!
>>
>>
>>
|
|
That's correct - the DNS 2Ks are Members. The AD domain is 2003 Interim,
existing DCs are all 2003. Does that change anything? I wasn't sure I could
promote the 2Ks to DCs in this environment, but if that's the case, your
outline makes the most sense.
The new 2003 DNS/DC can even take on the IP address of the 2K box being
retired, as it's the 2nd DNS for our clients.
"Danny Sanders" wrote:
[Quoted Text] > Sounds like the Win 2k DNS servers are not domain controllers? AD integrated
> DNS allows the DNS information to replicate along with the Active directory
> information, no special replication just for DNS like the primary/secondary
> model. Active Directory information is ONLY replicated to domain controllers
> and as a result AD integrated DNS is only available on a domain controller
> housing DNS.
>
> Suggest you promote the Win 2k server, the one you want to keep, to a domain
> controller. Set the DNS zone as AD integrated. Add the Win 2k3 server to the
> domain (you may have to run adprep if this is the first Win 2k3 server in
> the domain) and promote to a DC and the DNS info will replicate to the new
> Win 2k3 server.
>
> Done.
>
> Now you have 2 AD integrated DNS servers and a Win 2k server on old hardware
> that you can do with what you want.
>
>
> hth
> DDS
|
|
You don't have AD integrated dns if they are not member servers. Just add
dns to a DC make it a secondary to your primary server, allow replication to
work and then flip the dns server from secondary to AD integrated. Point
your dns clients to this new dns server add the dns service to the other
dc's you wish to have dns on and then you should be able to remove the old
dns servers.
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
"Chris U" <ChrisU[ at ]discussions.microsoft.com> wrote in message
news:FAD69F59-883F-4C4F-8AC0-49AAEEBFF3CC[ at ]microsoft.com...
[Quoted Text] > That's correct - the DNS 2Ks are Members. The AD domain is 2003 Interim,
> existing DCs are all 2003. Does that change anything? I wasn't sure I
> could
> promote the 2Ks to DCs in this environment, but if that's the case, your
> outline makes the most sense.
>
> The new 2003 DNS/DC can even take on the IP address of the 2K box being
> retired, as it's the 2nd DNS for our clients.
>
> "Danny Sanders" wrote:
>
>> Sounds like the Win 2k DNS servers are not domain controllers? AD
>> integrated
>> DNS allows the DNS information to replicate along with the Active
>> directory
>> information, no special replication just for DNS like the
>> primary/secondary
>> model. Active Directory information is ONLY replicated to domain
>> controllers
>> and as a result AD integrated DNS is only available on a domain
>> controller
>> housing DNS.
>>
>> Suggest you promote the Win 2k server, the one you want to keep, to a
>> domain
>> controller. Set the DNS zone as AD integrated. Add the Win 2k3 server to
>> the
>> domain (you may have to run adprep if this is the first Win 2k3 server in
>> the domain) and promote to a DC and the DNS info will replicate to the
>> new
>> Win 2k3 server.
>>
>> Done.
>>
>> Now you have 2 AD integrated DNS servers and a Win 2k server on old
>> hardware
>> that you can do with what you want.
>>
>>
>> hth
>> DDS
>
|
|
|