Changing DNS servers

[Denis Caron]

I've been searching the knowledge base, and perusing this newsgroup, but I'd
like some clarification - before I destroy my domain ;O)

I currently have two Win2000 DNS servers. Both are running on domain servers
in a child AD domain (I know - poor setup). I want to move at least one of
those DNS servers to one of the domain servers at the top of the forest. All
DNS servers are AD integrated.

Can I do the following ?

- Activate the DNS service on one (or both) of the top domain servers.
- Tell the existing DNS server that the new servers are now to receive
copies of the zones (let it sit for a few days, so it replicates - any way
to force replication ?).
- On the old master server, point the "primary server" zone configuration
info to the new server (let it sit for a few days, so it replicates - any
way to force replication ?).
- Set the DNS pointers from the parent and child domain servers to the new
DNS server and reboot the servers.
- Disable the DNS service on the old DNS servers

My main concern is that I wouldn't loose the Domain DNS information, so I
wouldn't "loose" my domain.

Thanks.

(e-mail address removed)

 

[Herb Martin]

I currently have two Win2000 DNS servers. Both are running on domain
servers

in a child AD domain (I know - poor setup).

There is nothing inherently or obvious wrong about the above.
In fact for many people that is the BEST setup.

I want to move at least one of
those DNS servers to one of the domain servers at the top of the forest. All
DNS servers are AD integrated.

General rule: The DNS for the zone supporting an Active Directory
Domain should run on the machines OF that domain. While this is
not a strong rule if you don't use AD-Integrated DNS, it is usually
a good idea and...

AD-DNS is usually a MUCH BETTER choice and for all practical
purposes should always run on the DCs of the SAME domain.

Can I do the following ?

- Activate the DNS service on one (or both) of the top domain servers.
- Tell the existing DNS server that the new servers are now to receive
copies of the zones (let it sit for a few days, so it replicates - any way
to force replication ?).

Sure -- normal way to move DNS around when you only have one or
a few domains. Make a secondary, slurp the records, change the DNS
server roles (e.g., new secondary to Primary etc.)

My main concern is that I wouldn't loose the Domain DNS information, so I
wouldn't "loose" my domain.

Why are you messing with what is WORKING?

You method is correct -- your motivation is unclear.
What problem are you actually trying to solve?

You aren't running the TOP domain DNS on the child
domains are you?

If not, don't move the child AD-integrated to the top;
leave it alone.

 

[Denis Caron]

Thank you for your reply.

Indeed, the problem is that my DNS servers are in the child domains, so when
the top domain starts it's got some startup problems - shall we say ?
My network isn't big enough to warrant 4 DNS servers, but I imagine I could
just move one of the DNS servers to the top domain, have it act as the
primary for the top domain. Leave another DNS server in the child domain and
have it act as the DNS primary for the child.
Then have both act as each other's secondary.

I would have thought it would be better to put both DNS servers in the two
domain controllers in the top domain (neither controller is doing much).

 

[Herb Martin]

Even looking at your first post, I am confused about what you have
and what you really want.

Indeed, the problem is that my DNS servers are in the child domains, so when
the top domain starts it's got some startup problems - shall we say ?
My network isn't big enough to warrant 4 DNS servers, but I imagine I

could

Well if it big enough for multiple domain it is at least big enough
for that many DNS zone servers - and likely that many DNS
servers or more.

NOTE: Multiple zones can be loaded on one server.

Each DC can be the dns server -- which is usually better.

just move one of the DNS servers to the top domain, have it act as the

A DNS server doesn't HAVE to be in that zone -- Register.Com
holds thousands of zones for various domains without being "part of
them"

primary for the top domain. Leave another DNS server in the child domain and
have it act as the DNS primary for the child.
Then have both act as each other's secondary.

You can add a secondary zone to all the "other zone" servers.
(Cross secondary support.)

I would have thought it would be better to put both DNS servers in the two
domain controllers in the top domain (neither controller is doing much).

Put the DNS zones for the top domain THERE -- hold secondaries if
you must.