Move DNS services to another 2000 AS

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

I'm going to be moving the DNS configs from one PC to another, but I'm
unsure as how to "backup" the existing server. Heres my plan:

1) Backup existing server setup (somehow)
2) Restore onto new server
3) Update DHCP to use new server
4) Set old server to forward to the new one

The reason behind this is that I'm setting up a Active Directory on a
new subnet, but the old server can't move across yet, and I can
interrupt "service".

So whats the best way of doing 1) and 2) ?

Adrian

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:eIJQAQAbEHA.3204@TK2MSFTNGP09.phx.gbl,
Adrian Marsh <hidden@somewhere.com> asked for help and I offered my
suggestions below:
> I'm going to be moving the DNS configs from one PC to another, but I'm
> unsure as how to "backup" the existing server. Heres my plan:
>
> 1) Backup existing server setup (somehow)
> 2) Restore onto new server
> 3) Update DHCP to use new server
> 4) Set old server to forward to the new one
>
> The reason behind this is that I'm setting up a Active Directory on a
> new subnet, but the old server can't move across yet, and I can
> interrupt "service".
>
> So whats the best way of doing 1) and 2) ?
>
> Adrian

Not exactly sure of your intention on creating a whole new AD Forest, Tree,
Domain or just another DC in an existing domain. Either way, its not always
necessary to have a DNS server over there when you set it up. We can always
move it later after the promotion. What do you currently have and can you
elaborate a bit more?

The easiest way to 'move' a zone elsewhere is to create a secondary zone on
the new server. Let the transfer happen. Then change it on the new server to
a Primary zone. But depending on your scenario above, there are other ways
to do it and other factors possibly involved, such as AD Integrated zones,
etc.


--
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 - Active Directory

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

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Ace,

Thanks for the reply.

Theres no existing Domain. They have a bunch of servers and w2k pro
machines (probably 50 in all). Theres a local DNS and DHCP server for
those machines, and they're all spread over about 3 private networks.

Our IT group want me to move these machines to a new subnet - one thats
more friendly with the IT network. So at the same time I'm building the
AD infastructure, so I can maintain the PCs better in the future.

I can't afford the existing single DNS server to go off-line until the
new one is populated and running for at least 3 days, so that the
existing PCs migrate across. So what I need is a way of backing-up the
DNS setup and copying it to the new machine.

Any advice offered is appreciated.

Adrian


Ace Fekay [MVP] wrote:
> In news:eIJQAQAbEHA.3204@TK2MSFTNGP09.phx.gbl,
> Adrian Marsh <hidden@somewhere.com> asked for help and I offered my
> suggestions below:
>
>>I'm going to be moving the DNS configs from one PC to another, but I'm
>>unsure as how to "backup" the existing server. Heres my plan:
>>
>>1) Backup existing server setup (somehow)
>>2) Restore onto new server
>>3) Update DHCP to use new server
>>4) Set old server to forward to the new one
>>
>>The reason behind this is that I'm setting up a Active Directory on a
>>new subnet, but the old server can't move across yet, and I can
>>interrupt "service".
>>
>>So whats the best way of doing 1) and 2) ?
>>
>>Adrian
>
>
> Not exactly sure of your intention on creating a whole new AD Forest, Tree,
> Domain or just another DC in an existing domain. Either way, its not always
> necessary to have a DNS server over there when you set it up. We can always
> move it later after the promotion. What do you currently have and can you
> elaborate a bit more?
>
> The easiest way to 'move' a zone elsewhere is to create a secondary zone on
> the new server. Let the transfer happen. Then change it on the new server to
> a Primary zone. But depending on your scenario above, there are other ways
> to do it and other factors possibly involved, such as AD Integrated zones,
> etc.
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:OQvkAUFbEHA.1644@tk2msftngp13.phx.gbl,
Adrian Marsh <hidden@somewhere.com> asked for help and I offered my
suggestions below:
> Ace,
>
> Thanks for the reply.
>
> Theres no existing Domain. They have a bunch of servers and w2k pro
> machines (probably 50 in all). Theres a local DNS and DHCP server for
> those machines, and they're all spread over about 3 private networks.
>
> Our IT group want me to move these machines to a new subnet - one
> thats more friendly with the IT network. So at the same time I'm
> building the AD infastructure, so I can maintain the PCs better in
> the future.
>
> I can't afford the existing single DNS server to go off-line until the
> new one is populated and running for at least 3 days, so that the
> existing PCs migrate across. So what I need is a way of backing-up
> the DNS setup and copying it to the new machine.
>
> Any advice offered is appreciated.
>
> Adrian


I see. Hope you do some homework on how to design AD and its requirements.
For a 50 user network, its relatively easy.

As for moving the zones, The Primary zone transfer to a secondary zone is
probably your best bet. Either way, its only a text file to backup. Assuming
its currently on a Windows machine, you can backup the DNS registry key as
well. You can opt to backup the system too with a tape backup (system
state). There is no 'rt-click' feature like some of the other functions
have, unfortunately, but its really easy since there's not much to DNS.

Not knowing how far along you are with designing or if you took any classes
(highly recommended), I thought to provide some links for you:

254680 - DNS Namespace Planning:
http://support.microsoft.com/default.aspx?scid=kb;en-us;254680

285983 - Considerations for Designing Namespaces in Windows 2000-Based
Domain:
http://support.microsoft.com/default.aspx?scid=kb;en-us;285983

Active Directory - All about it [For Design see section on Planning &
Deployment Guides]:
http://www.microsoft.com/windows2000/technologies/directory/ad/default.asp

Chapter 4 - Active Directory Design:
http://www.microsoft.com/resources/documentation/exchange/2000/all/reskit/en-us/part2/c04names.mspx

Chapter 9 - Designing the Active Directory Structure:
http://www.microsoft.com/resources/documentation/windows/2000/server/reskit/en-us/deploy/part3/chapt-9.mspx

Deploying and Designing Active Directory [DNS Design, Migration, Cert Auth,
Branch Offices, Exchange, ADC, Import-Export, etc]:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/deploy/default.mspx

Deployment Planning Guide:
http://www.microsoft.com/windows2000/techinfo/reskit/dpg/default.asp


--
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 - Active Directory

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