Windows 2003 DNS uppgrade

  • Thread starter Thread starter Craig
  • Start date Start date
C

Craig

Hi we are migrating to windows 2003 and we have 2 AD
integrated DNS servers,one primary and one secondary.
My question is if i do a clean install of the primary
integrated DNS server to windows 2oo3 will the DNS
configuration from the secondary replicate back if the
server has the same name and ip etc ??

Regards Craig
 
In
Craig said:
Hi we are migrating to windows 2003 and we have 2 AD
integrated DNS servers,one primary and one secondary.
My question is if i do a clean install of the primary
integrated DNS server to windows 2oo3 will the DNS
configuration from the secondary replicate back if the
server has the same name and ip etc ??

Regards Craig
Click to expand...


With all due respect, you're terminology is somewhat skewed. As far as
terminilogy, there is no "Primary" or "Secondary" DNS "servers". Maybe you
have two DNS servers, and you've selected one to be used as the first and
the other as the second in your IP properties?

As for a clean install, keep in mind, when you install a fresh copy of an
OS, it creates a new SID and everything else, so, what I'm saying is if you
cleanly install a machine, using the same name as the previous machine
(assuming you removed it from the network and demoted it properly from a DC
to a member server), then you promoted the new machine to become a DC into
the existing domain, then yes, since AD Integrated zones are stored in AD
and when you install DNS on the new machine, and then create that zone in
DNS and make it AD Integrated, then it pulls the data out of AD's database.

On the other hand, if you install a fresh machine, install DNS on it, create
a secondary "zone" and tell it the MASTER IP is the other server *(your term
for your "primary"), and zone transfers are allowed, then a zone transfer
will occur and you get the data. Even if the other server is AD Integrated,
and you allow zone transfers and create a secondary elsewhere, it will
transfer. If the machine is a DC in the same domain, and you create an AD
Integrated zone, then it will pop up as mentioned in the prev paragraph.

You have to be careful with using the same names especially if they are AD
members due to the SID numbers, especially if they're DCs, since assuming
it's a DC since you mentioned "AD Integrated" zones.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Hi sorry for the terminology abuse, yes they are
both AD integrated DNS´s and DC´s with the Global
catalog function. And now that we are installing
windows 2003 i would prefer to do a clean install.
So i would lean towards reomoving the global catalog
from the server and the running dc promo and removing
it from the network, the reinstlling with a clean install
of Windows 2003.

Thanks for the tip about the SIDS, would appreciate any
other comments about problems that could occur.

Regards Craig
 
In
Hi sorry for the terminology abuse, yes they are
both AD integrated DNS´s and DC´s with the Global
catalog function. And now that we are installing
windows 2003 i would prefer to do a clean install.
So i would lean towards reomoving the global catalog
from the server and the running dc promo and removing
it from the network, the reinstlling with a clean install
of Windows 2003.

Thanks for the tip about the SIDS, would appreciate any
other comments about problems that could occur.

Regards Craig
Click to expand...
I see, that gives me a clearer picture. If you want to install fresh,
meaning a whole new domain in a new forest, then no, the DNS data won't come
across since they are in different AD domins and would need to rely on zone
transfers. But keep in mind you'll need to migrate your users over using
ADMT.

If in the same domain and forest, I would suggest to promote the W2k3 server
into the current domain. But you have to run ADPrep first to prep the
current W2k database to be compatible with W2k3's AD database.

331161 - Hotfixes to Install on Windows 2000 Domain Controllers Before
Running Adprep -Forestprep:
http://support.microsoft.com/?kbid=331161

325379 - How to Upgrade Windows 2000 Domain Controllers to Windows Server
2003:
http://support.microsoft.com/?id=325379

Download details Active Directory Migration Tool v.2.0:
http://microsoft.com/downloads/deta...b1-5849-4707-9817-8c9773c25c6c&DisplayLang=en

Windows Server 2003 Upgrade Assistance Center:
http://www.microsoft.com/windowsserver2003/upgrading/nt4/upgradeassistance/default.mspx

New Active Directory Features in Windows Server 2003, Part 1:
http://www.serverwatch.com/tutorials/article.php/2213281

DNS zone types:
http://www.serverwatch.com/tutorials/article.php/2226201

Choosing a Zone Type:
http://www.microsoft.com/technet/pr...r2003/proddocs/deployguide/dnsbd_dns_nuql.asp

New Features in Win 2003 DNS:
http://www.microsoft.com/technet/tr...proddocs/standard/sag_DNS_ovr_NewFeatures.asp

816584 - HOW TO- Set Up the Domain Name System for Active Directory in
Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816584

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top