Oscar
Guest
|
 Posted:
Sun Jan 30, 2005 1:47 am Post subject:
DNS move to new DC |
|
|
I have one server (SRV1) DC that has DNS, DHCP and WINS but I transfer all
the 5 roles to a new server (Server2) DC that now has all the five roles,
DHCP and WINS, there's a tech document how to move the the DNS to the SRV2?
I have Exchange 2k running too, it will be an effect over this if the IP
Addrss of SRV2 is not the same?
Thanks,
Oscar |
|
Herb Martin
Guest
|
| Posted:
Sun Jan 30, 2005 2:38 am Post subject:
Re: DNS move to new DC |
|
|
"Oscar" <Oscar@discussions.microsoft.com> wrote in message
news:702BEED8-C9FD-4CE9-9168-5E17564E3284@microsoft.com...
| Quote: | I have one server (SRV1) DC that has DNS, DHCP and WINS but I transfer all
the 5 roles to a new server (Server2) DC that now has all the five roles,
DHCP and WINS, there's a tech document how to move the the DNS to the
SRV2? |
DNS is almost trivial to transfer if you only have
one zone/domain.
If you use a Primary, make the other machine a Secondary;
replicate (zone transfer); [change the client settings]; swap
roles; remove the old one from DNS.
If you use a AD-Integrated you can just make the other DC
another AD-integrated zone/server (assuming your replication
is working and completed the other DC has the records
already), [change the client settings] and then remove the zone
from the earlier server.
REMEMBER: Servers are DNS clients too so you must
be sure to change the NIC->IP options on every computer.
Remember the GC too (if you plan to remove the old DC).
| Quote: | I have Exchange 2k running too, it will be an effect over this if the IP
Addrss of SRV2 is not the same?
|
It might but it isn't clear where everything is now,
especially the Exchange.
The GC becomes even more critical.
Also, when you prepare to remove the old DC, be sure to
do the DCPromo while it is STILL ONLINE -- this will
remove it from AD properly etc.
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domain (either directly or indirectly)
Restart NetLogon on any DC if you change any of the above that
affects a DC and/or use:
nltest /dsregdns /server:DC-ServerNameGoesHere
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
--
Herb Martin
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in