You can make a secondary zone. Then make that zone a primary (which cuts the
knot from the previous primary). You can make any zone Integrated. It just
means it is stored in AD and replicated to other DCs.
I think the concept of integrated is a little confusing.
- There is integrated as in the domain zone, which holds the DC records and
is updated by domain clients
- and there is integrated as in Stored in the AD but nothing to do with the
domain.
If you are talking about a zone that you need to keep, but is not the new AD
zone, I suggest making it a secondary then primary. That just moves the
primary from the NT server to the W2K3 server. You can decide what to do
with it later,
Anthony



"Z" <Z@discussions.microsoft.com> wrote in message
news:86E2CE52-A445-4E51-AAFE-CB5788A7B4C9@microsoft.com...
> Hello,
>
> I have 3 Windows 2003 DNS servers running standard primary and secondary
> in
> a Windows NT 4 domain. We're going to migrate to AD (new domain) and
> leave
> the NT4 domain behind for decomm.
> What's the best way to get the zones from the primary DNS server in the
> NT4
> domain over to the domain controllers in AD, which will be configured to
> use
> AD integrated DNS? I saw a reference to a utility called DNSDump.cmd at
> www.reskit.net/scripts. Sounds like that would work, but I haven't looked
> at
> the script. I could probably use dnscmd to export the zones on the
> primary
> DNS server and import them on one of the DCs in AD.
> Thank you!
>