We currently have 2 domains in our forest. One domain has 2 w2k3 DC's
(domain2) and one domain has 2 w2k DC's (domain1). Recently someone added a
w2k3 server to (domain1) and promoted it to a DC. They then installed DNS and
setup (domain2) as a secondary DNS zone. The AD intigrated zone on (domain2)
disappeared some how. Event logs show that it was deleted somehow. Does
anyone know if this was a configuration problem by the installer or what?
> We currently have 2 domains in our forest. One domain has 2 w2k3 DC's
> (domain2) and one domain has 2 w2k DC's (domain1). Recently someone added
[quoted text clipped - 3 lines]
> somehow. Does anyone know if this was a configuration problem by the
> installer or what?
An administrator may have deleted it or, more likely, the creation of the
secondary zone with the same name as the AD-integrated zone (DomainDNSZone)
auto-deleted the DomainDNSZone zone. This new secondary zone replicated
through AD effectively overwriting the existing DomainDNSZone (and records).

Signature
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
Calvin - 30 Jul 2005 04:45 GMT
> > We currently have 2 domains in our forest. One domain has 2 w2k3 DC's
> > (domain2) and one domain has 2 w2k DC's (domain1). Recently someone added
[quoted text clipped - 8 lines]
> auto-deleted the DomainDNSZone zone. This new secondary zone replicated
> through AD effectively overwriting the existing DomainDNSZone (and records).
Todd J Heron - 30 Jul 2005 05:17 GMT
>> Is that something new for win2k3? The AD zone in (Domain2) and the
>> secondary zone in (domain1) were they same name before the upgrade and
>> had np problems.
I would say to re-explain this in more detail, including actual names, so we
can get an acccurate understanding of the true problem.

Signature
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
> We currently have 2 domains in our forest. One domain has 2 w2k3 DC's
> (domain2) and one domain has 2 w2k DC's (domain1). Recently someone
[quoted text clipped - 3 lines]
> that it was deleted somehow. Does anyone know if this was a
> configuration problem by the installer or what?
This would make me think that the zone for domain2 on the Win2k3 DC is set
to replicate to all DNS servers in the forest (with Win2k3). When you added
the Win2k3 DC in domain1 then the domain2 zone would replicate to it. But
since you created a secondary zone for domain2 it basically removed the zone
from AD. Convert the zone back to AD integrated, and leave it alone, don't
create any AD zones on the other DCs, the converted domain2 will replicate
back to the other Win2k3 servers without data loss.
This zone will NOT replicate to the Win2k server so they have to use
secondary zones.

Signature
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
Calvin - 30 Jul 2005 23:34 GMT
Thanks for the advise.
> > We currently have 2 domains in our forest. One domain has 2 w2k3 DC's
> > (domain2) and one domain has 2 w2k DC's (domain1). Recently someone
[quoted text clipped - 14 lines]
> This zone will NOT replicate to the Win2k server so they have to use
> secondary zones.