Migrating DNS info from a 2000 server to a 2003 server w AD

  • Thread starter Thread starter microsoft
  • Start date Start date
M

microsoft

Is there an easy way to import the DNS entries from a 2000 server to a 2003
server without overwriting any of the 2003 entries?
 
In
microsoft said:
Is there an easy way to import the DNS entries from a 2000 server to
a 2003 server without overwriting any of the 2003 entries?
Click to expand...

Well, if i'st a zone you're talking about, you can create the zone on the
2003 server as a secondary to the W2k's Primary zone, then let the transfer
happen, then make it Primary.

Not sure what you mean by "not overwriting any entries". What entries are on
there? Is it already a secondary or is it AD Integrated? If it's a different
zone, then it's a moot point.


--
Regards,
Ace

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

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

"Ace Fekay [MVP]"
In

Well, if i'st a zone you're talking about, you can create the zone on the
2003 server as a secondary to the W2k's Primary zone, then let the transfer
happen, then make it Primary.

Not sure what you mean by "not overwriting any entries". What entries are on
there? Is it already a secondary or is it AD Integrated? If it's a different
zone, then it's a moot point.


--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
Click to expand...
 
Ace said:
*In microsoft <[email protected]> posted their thoughts, then I offere
mine

Well, if i'st a zone you're talking about, you can create the zone o
the
2003 server as a secondary to the W2k's Primary zone, then let th
transfer
happen, then make it Primary.

Not sure what you mean by "not overwriting any entries". What entrie
are on
there? Is it already a secondary or is it AD Integrated? If it's
different
zone, then it's a moot point.


--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
Click to expand...


I have this situation too, but creating a secondary zone on the 2K
server isnt an option, as the domain zone name already exists, as a
AD-integrated zone.

I.e. on Windows 2000 server (in a Windows NT domain) I have a domai
called home.company.net, and now I also have a new 2K3 AD domain calle
home.company.net that the customer wants all the records transferre
from the old to the new...

Do you know of a way to do that? I've seen Dean Wells DNSdump.cmd, bu
I don't think it applies in my case as it appears will overwrite all m
existing zone info/config etc - quite dangerous seeing as it is a full
configured AD child domain.

Look forward to hearing from you,
Geoff


-
clow
 
In
clowg said:
I have this situation too, but creating a secondary zone on the 2K3
server isnt an option, as the domain zone name already exists, as an
AD-integrated zone.

I.e. on Windows 2000 server (in a Windows NT domain) I have a domain
called home.company.net, and now I also have a new 2K3 AD domain
called home.company.net that the customer wants all the records
transferred from the old to the new...

Do you know of a way to do that? I've seen Dean Wells DNSdump.cmd,
but I don't think it applies in my case as it appears will overwrite
all my existing zone info/config etc - quite dangerous seeing as it
is a fully configured AD child domain.

Look forward to hearing from you,
Geoff.
Click to expand...

I don't understand Geoff, you say you cannot create a secondary zone on 2k3
since the zone exists in the child domain? Then why not just set it as AD
Integrated since the zone is already there? Then change it back to a Primay.
Of course we're talking about machines in the same forest.

Now if you are saying you have a completey separate new domain in a new
forest that you want migrated, then the Primary/Secondary method is your
bet, unless you can tweak Dean's script.

You can also opt to use DNSCMD or just manually copy the
system32\dns\zonename.dns files over and use them.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
I don't understand Geoff, you say you cannot create a secondar
zone on 2k3
since the zone exists in the child domain? Then why not just set i
as AD
Integrated since the zone is already there? Then change it back to
Primay.
Of course we're talking about machines in the same forest.

Now if you are saying you have a completey separate new domain in
new
forest that you want migrated, then the Primary/Secondary method i
your
bet, unless you can tweak Dean's script.

You can also opt to use DNSCMD or just manually copy the
system32\dns\zonename.dns files over and use them.
Click to expand...


The source is a W2K DNS server in a Windows NT domain.
The destination is a completely new & seperate 2K3 AD domain/forest.

The zone home.company.net exists as the primary DNS zone in teh WIndow
NT domain. It was also (unfortunately) the DNS name that was chosen t
create the new child domain in the new forest.

I can't change the AD DNS zone to non-AD-integrated... HANG ON - I jus
went to check that setting, and now I see I can change it - I swear i
was greyed out when I tried this yesterday!!

That should solve it for me :-)

G


-
clow
 
In
clowg said:
The source is a W2K DNS server in a Windows NT domain.
The destination is a completely new & seperate 2K3 AD domain/forest.

The zone home.company.net exists as the primary DNS zone in teh
WIndows NT domain. It was also (unfortunately) the DNS name that was
chosen to create the new child domain in the new forest.

I can't change the AD DNS zone to non-AD-integrated... HANG ON - I
just went to check that setting, and now I see I can change it - I
swear it was greyed out when I tried this yesterday!!

That should solve it for me :-)

G.
Click to expand...

Oh, I see! NT4 to W2k3. There's third party stuff for that other than the
Primary/Secondary method.

But I'm glad you got it to work!

:-)

Ace
 
Back
Top