DNS root zone issue - need a real guru for this one

Here is the situation:

We have two dns servers in the parent domain, on one dns server with a '.' on
it, this was done for security reasons. There is a child domain that
administers their own dns servers. All zones are AD integrated. Everything
was working fine. An admin in the parent domain decided to create a new '.'
zone on the second dns server in the parent domain. After replication
occurred, this "new" '.' zone was replicated to the child domain and I think
the original '.' zone was overwritten. Does this sound plausible? Question is
why wasn't the original '.' zone replicated to the second dns server in the
parent domain, but when a new '.' was created on the second dns server it was
replicated to the child domain? We are trying to determine what happened and
if our conclusions are correct.  Any help would be great. Thanks.
Who is Participating?
The original root zone was set to replicate to all DNS servers in the Domain - therefore, it didn't propogate to the child domains.

The new zone was created and set to replicate to all DNS servers in the Forest - and did.

What leads someone to believe that a root zone promotes security?

wayy2beAuthor Commented:
I am not sure, it is contrary to everything I know. So in your opinion the new root zone, when replicated to all DNS servers in the forest, did overwrite the original root?
It probably would have, given the name and the partition it was created in.

Just double-check the replication scope on that zone - if it's to all DNS servers in the Forest, then you have your answer.
wayy2beAuthor Commented:
Just checked and you are 100% correct!  Thanks for your help!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.