Tennessee_Pride
asked on
Event ID 4515
upon rebooting the PDC emulator, FSMO AD controller, it takes about 10 minutes for the system to boot. During that time, havoc tends to reign. In the event view I found the event id 4515 and follow the kb link to this
http://support.microsoft.com/kb/867464/en-us
Event ID: 4515
Event Source: DNS
Event Type: Warning
Event Description: The zone contoso.com was previously loaded from the directory partition ForestDnsZones.contoso.com but another copy of the zone has been found in directory partition DomainDnsZones.contoso.com . The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
The problem Im having are these
1) I'm showing the _msdcs zone getting previously loaded from the MicrosoftDNS zone but it finds the 2nd one in the ForestDNSZone. It says its ignoring the forest and running with the MicrosoftDNS
"The zone _msdcs.corp.tnpride.com was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition ForestDnsZones.corp.tnprid e.com. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible. "
2) in ADSI edit, when I try to connect to Distinguished Name or Naming Context 'DC=MicrosoftDNS.DC=mydoma in,DC=com it says 'Directory object not found'
3) There is a MicrosoftDNS inside of the DomainDNS but is doesn't have the _msdcs in it.
I'm not to keen on deleting the one in the ForestDNS if I can't find a copy somewhere else
Not really sure what to do
http://support.microsoft.com/kb/867464/en-us
Event ID: 4515
Event Source: DNS
Event Type: Warning
Event Description: The zone contoso.com was previously loaded from the directory partition ForestDnsZones.contoso.com
The problem Im having are these
1) I'm showing the _msdcs zone getting previously loaded from the MicrosoftDNS zone but it finds the 2nd one in the ForestDNSZone. It says its ignoring the forest and running with the MicrosoftDNS
"The zone _msdcs.corp.tnpride.com was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition ForestDnsZones.corp.tnprid
2) in ADSI edit, when I try to connect to Distinguished Name or Naming Context 'DC=MicrosoftDNS.DC=mydoma
3) There is a MicrosoftDNS inside of the DomainDNS but is doesn't have the _msdcs in it.
I'm not to keen on deleting the one in the ForestDNS if I can't find a copy somewhere else
Not really sure what to do
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hmm...I also have
The zone corp.tnpride.com was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.corp.tnprid e.com. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible.
there as well
so
_msdcs and corp are both being loaded from MicrosoftDNS which looks like they are both being loaded from the area mentioned in option three of said kb article posted earlier. Does it look like the zones are being loaded from the Domain NC first and then the Forest and Domain? If so...what do I delete.
To summarize the zones I am seeing thru adsiedit
1) DC=ForestDNS/CN=MicrosoftD NS/CN=_msd cs.domain. com
2)DC=DomainDNSZones/CN=cor p.domain.c om
DC=DomainDNSZones/146.in-a ddr.arpa
DC=DomainDNSZones/CN=RootD NSServers
3) Domain/domain.com/CN=Syste m/CN=Micro softDNS/DC =_msdcs.do main.com
Domain/domain.com/CN=Syste m/CN=Micro softDNS/DC =corp.doma in.com
Domain/domain.com/CN=Syste m/CN=Micro softDNS/Ro otDNSServe rs
The zone corp.tnpride.com was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.corp.tnprid
there as well
so
_msdcs and corp are both being loaded from MicrosoftDNS which looks like they are both being loaded from the area mentioned in option three of said kb article posted earlier. Does it look like the zones are being loaded from the Domain NC first and then the Forest and Domain? If so...what do I delete.
To summarize the zones I am seeing thru adsiedit
1) DC=ForestDNS/CN=MicrosoftD
2)DC=DomainDNSZones/CN=cor
DC=DomainDNSZones/146.in-a
DC=DomainDNSZones/CN=RootD
3) Domain/domain.com/CN=Syste
Domain/domain.com/CN=Syste
Domain/domain.com/CN=Syste
ASKER
I also have no 2000 DC's
ASKER
I stopped the dns on the other two DC's, Changed the three zones _msdsc, domain.com, and thereverse lookup zone all to non AD intergrated-primary...rest arted the dns service and still get the same error
ASKER
This is thesame question I asked previous and I think Ill be taking this route this week
https://www.experts-exchange.com/questions/22401330/Various-issues-on-Rebooting-a-2003-AD-Domain-controller.html
Only thing is in adsi edit the _msdcs zone is in both the doman and forest partition. So My plan is to delete the entire DomainDNS partition, delete my DNS Zones and recreate them as AD integrated and reboot the systems and register etc. Sound right?
https://www.experts-exchange.com/questions/22401330/Various-issues-on-Rebooting-a-2003-AD-Domain-controller.html
Only thing is in adsi edit the _msdcs zone is in both the doman and forest partition. So My plan is to delete the entire DomainDNS partition, delete my DNS Zones and recreate them as AD integrated and reboot the systems and register etc. Sound right?
ASKER
I fixed it by deleting the DomainDNS partition and restarting
ASKER