Exporting dns entrys

  • Thread starter Thread starter RIP
  • Start date Start date
R

RIP

The time has come for my buissness to upgrade servers. We
have purchased a new server running 2k3. There are quite
a few entrys in our old 2k AS dns server. Is there a way
i can export all the entry's, then import them into new
server? i tried doing export list from right click on
forward, but it outputs a list of the companys domains, is
there a way i can export ALL the data so its all in one
easy file to import on new server? I will also be needing
to do this for IIS if anybody has suggestions.
 
The short answer is that if these domains are
AD-integrated, letting AD replication do the
job is simplest. This assumes both servers
are turned up at the same time.

Second way would be to create the zones on
the new server as secondaries, let them transfer
over, then switch them to primary or AD-integrated.

Finally, you can first convert the zones to
standard primary (if necessary), then right-click each
zone and do an "update data file", which will create corresponding
*.dns files in the system32\dns folder, You can use
these .dns files to import on the new server.

For AD zones, I'd recommend running a netdiag /fix
after the import.

There are some other fine points to this depending on
how you are setup, but this should get you going.

Steve Duff, MCSE
Ergodic Systems, Inc.
 
perfect answer, it worked. thanks you saved me ALOT of time
-----Original Message-----
The short answer is that if these domains are
AD-integrated, letting AD replication do the
job is simplest. This assumes both servers
are turned up at the same time.

Second way would be to create the zones on
the new server as secondaries, let them transfer
over, then switch them to primary or AD-integrated.

Finally, you can first convert the zones to
standard primary (if necessary), then right-click each
zone and do an "update data file", which will create corresponding
*.dns files in the system32\dns folder, You can use
these .dns files to import on the new server.

For AD zones, I'd recommend running a netdiag /fix
after the import.

There are some other fine points to this depending on
how you are setup, but this should get you going.

Steve Duff, MCSE
Ergodic Systems, Inc.

"RIP" <[email protected]> wrote in
message news:[email protected]...
 
i should prolly add that i had to go into the registry and
export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\DNS Server and import onto new server.
easy fix
-----Original Message-----
The short answer is that if these domains are
AD-integrated, letting AD replication do the
job is simplest. This assumes both servers
are turned up at the same time.

Second way would be to create the zones on
the new server as secondaries, let them transfer
over, then switch them to primary or AD-integrated.

Finally, you can first convert the zones to
standard primary (if necessary), then right-click each
zone and do an "update data file", which will create corresponding
*.dns files in the system32\dns folder, You can use
these .dns files to import on the new server.

For AD zones, I'd recommend running a netdiag /fix
after the import.

There are some other fine points to this depending on
how you are setup, but this should get you going.

Steve Duff, MCSE
Ergodic Systems, Inc.

"RIP" <[email protected]> wrote in
message news:[email protected]...
 
Back
Top