W2003 DNS Event 4515 "Gerhard K. Ziran" <no[ at ]spam.com> 6/28/2007 9:14:31 AM I am putting the finishing touches to our new 2003 ENT 64 server. Our old NT4 servers are still running as BDC's, soon to be decommissioned. I still have one warning message in the new server's DNS event log: Event ID 4515: The zone domain.com was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDnsZones.domain.com. The DNS Server will ignore this new copy of the zone. Please resolve this conflict as soon as possible. The DNS server shows two forward lookup zones, domain.com and _msdcs.domain.com. All DNS entries are in the domain.com zone and DNS seems to work okay. There is only the one domain in our network. I have checked the KB article 867464, but would like to be sure how to proceed. The _msdcs subdomain seems to be located under the ForestDNSZones, domain.com under DomainDNSZones. Can I savely go ahead and delete the _msdcs zone? Thanks!

Re: W2003 DNS Event 4515 "Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 6/28/2007 12:39:39 PM Read inline please. In news:ORUJ$SWuHHA.3640[ at ]TK2MSFTNGP05.phx.gbl, Gerhard K. Ziran <no[ at ]spam.com> typed: [Quoted Text] > I am putting the finishing touches to our new 2003 ENT 64 server. > Our old NT4 servers are still running as BDC's, soon to be > decommissioned. I still have one warning message in the new server's > DNS event log: > > Event ID 4515: The zone domain.com was previously loaded from the > directory partition MicrosoftDNS but another copy of the zone has > been found in directory partition DomainDnsZones.domain.com. The DNS > Server will ignore this new copy of the zone. Please resolve this > conflict as soon as possible. > > The DNS server shows two forward lookup zones, domain.com and > _msdcs.domain.com. All DNS entries are in the domain.com zone and DNS > seems to work okay. There is only the one domain in our network. > > I have checked the KB article 867464, but would like to be sure how to > proceed. The _msdcs subdomain seems > to be located under the ForestDNSZones, domain.com under > DomainDNSZones. Can I savely go ahead and delete the _msdcs zone? No! Do not delete this zone, this zone contains the Forest Wide Netlogon registered records and is created by default under Windows Server 2003. Did I hear you say anything about deleting the _msdcs Delegation in the domain.com zone? (That's why I said no.) You are apparently getting this warning because you moved the domain.com zone from the MicrosoftDNS partition to the DomainDNSZones partition, it may be a temporary warning, if you continually get this warning, change the domain.com zone to a Standard Primary zone (Clear the "Store in Active Directory" check box) use Adsiedit to delete the domain.com zone objects from both partitions (Don NOT delete the _msdcs.domain.com zone objects) restart the DNS service, then place the zone back in AD and set the replication scope. Word of advice, the next time you change the replication scope, change the zone to standard primary, force a replication cycle, then put the zone back in AD into the replication scope you want it changed to. I have found that by doing this, you don't get these warnings. -- Best regards, Kevin D. 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/ http://support.wftx.us/ http://message.wftx.us/ =================================== 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 ===================================

Re: W2003 DNS Event 4515 "Gerhard K. Ziran" <no[ at ]spam.com> 6/29/2007 6:41:57 AM Hi Kevin. Thanks for the reply. The warning comes once after every system start. I did not specifically change the replication scope - the current setup is the result of migrating from NT4 to W2003 and new hardware; probably from the old PDC that was upgraded in place, then taken out after the new server took over. That's also my first experience with 2003, so please bear with me if I seem slow to catch up. Okay then ... I should take the domain.coim zone out of AD in DNSmgmt. Clear. In Adsiedit, I only have one instance of domain.com, under DC=DomainDNSZones / CN=MicrosoftDNS. Likewise, _msdcs.domain.com is only found under DC=ForestDNSZones / CN=MicrosoftDNS. I should then leave _msdcs alone and delete the complete domain.com entry from DomainDNSZones. Correct? Restart DNS, back to DNSmgmt and put the zone back in AD. Also clear. Did I get that all correctly? Thanks, Gerd _________________________________________________________________________________ Tu's nicht - die Flecken gehen so schwer aus dem Teppich. "Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> schrieb im Newsbeitrag news:ei85lFYuHHA.3480[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > No! > Do not delete this zone, this zone contains the Forest Wide Netlogon > registered records and is created by default under Windows Server 2003. > > Did I hear you say anything about deleting the _msdcs Delegation in the > domain.com zone? (That's why I said no.) > > You are apparently getting this warning because you moved the domain.com > zone from the MicrosoftDNS partition to the DomainDNSZones partition, it > may > be a temporary warning, if you continually get this warning, change the > domain.com zone to a Standard Primary zone (Clear the "Store in Active > Directory" check box) use Adsiedit to delete the domain.com zone objects > from both partitions (Don NOT delete the _msdcs.domain.com zone objects) > restart the DNS service, then place the zone back in AD and set the > replication scope. > Word of advice, the next time you change the replication scope, change the > zone to standard primary, force a replication cycle, then put the zone > back > in AD into the replication scope you want it changed to. I have found that > by doing this, you don't get these warnings. > > -- > Best regards, > Kevin D. Goodknecht Sr. [MVP] > Hope This Helps

Re: W2003 DNS Event 4515 "Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> 6/29/2007 4:31:25 PM Read inline please. In news:eIblYihuHHA.1168[ at ]TK2MSFTNGP02.phx.gbl, Gerhard K. Ziran <no[ at ]spam.com> typed: [Quoted Text] > Hi Kevin. > > Thanks for the reply. The warning comes once after every system > start. I > did not specifically change the replication scope - the current setup > is the > result of migrating from NT4 to W2003 and new hardware; probably from > the > old PDC that was upgraded in place, then taken out after the new > server took > over. That's also my first experience with 2003, so please bear with > me if > I seem slow to catch up. > > Okay then ... I should take the domain.coim zone out of AD in DNSmgmt. > Clear. > > In Adsiedit, I only have one instance of domain.com, under > DC=DomainDNSZones > / CN=MicrosoftDNS. Likewise, _msdcs.domain.com is only found under > DC=ForestDNSZones / CN=MicrosoftDNS. > > I should then leave _msdcs alone and delete the complete domain.com > entry > from DomainDNSZones. Correct? You should delete the conflicting object, it usually has a 'cnf' in its name, by default the zone should be in the MicrosoftDNS Domain replication partition, which you can also see in the System Container in ADU&C in Advanced view. The ForestDNSZones and DomainDNSZones can only be viewed in ADSIEdit > > Restart DNS, back to DNSmgmt and put the zone back in AD. Also clear. > Did I get that all correctly? Yes, but I'll clarify, change the zone to a Standard Primary, which removes it from AD. Sometimes, this is all you need to do to clear it up because this action alone should delete the objects from AD. -- Best regards, Kevin D. 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/ http://support.wftx.us/ http://message.wftx.us/ =================================== 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 ===================================

Re: W2003 DNS Event 4515 "Gerhard K. Ziran" <no[ at ]spam.com> 7/2/2007 9:10:16 AM Kevin, FYI, I seem to have it up and running now. I just took out the zone from AD, added it back in after restarting the DNS server and set the replication scope. The last two daily restarts went off without the 4515 error. Thanks for your help! Gerd _________________________________________________________________________________ "Kevin D. Goodknecht Sr. [MVP]" <admin[ at ]nospam.WFTX.US> schrieb im Newsbeitrag news:Oo7MxrmuHHA.1168[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] > Read inline please. > > In news:eIblYihuHHA.1168[ at ]TK2MSFTNGP02.phx.gbl, > Gerhard K. Ziran <no[ at ]spam.com> typed: >> Hi Kevin. >> >> Thanks for the reply. The warning comes once after every system >> start. I >> did not specifically change the replication scope - the current setup >> is the >> result of migrating from NT4 to W2003 and new hardware; probably from >> the >> old PDC that was upgraded in place, then taken out after the new >> server took >> over. That's also my first experience with 2003, so please bear with >> me if >> I seem slow to catch up. >> >> Okay then ... I should take the domain.coim zone out of AD in DNSmgmt. >> Clear. >> >> In Adsiedit, I only have one instance of domain.com, under >> DC=DomainDNSZones >> / CN=MicrosoftDNS. Likewise, _msdcs.domain.com is only found under >> DC=ForestDNSZones / CN=MicrosoftDNS. >> >> I should then leave _msdcs alone and delete the complete domain.com >> entry >> from DomainDNSZones. Correct? > > You should delete the conflicting object, it usually has a 'cnf' in its > name, by default the zone should be in the MicrosoftDNS Domain replication > partition, which you can also see in the System Container in ADU&C in > Advanced view. The ForestDNSZones and DomainDNSZones can only be viewed in > ADSIEdit > >> >> Restart DNS, back to DNSmgmt and put the zone back in AD. Also clear. > > >> Did I get that all correctly? > > Yes, but I'll clarify, change the zone to a Standard Primary, which > removes > it from AD. Sometimes, this is all you need to do to clear it up because > this action alone should delete the objects from AD. > > > > > > -- > Best regards, > Kevin D. 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/ > http://support.wftx.us/ > http://message.wftx.us/ > =================================== > 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 > =================================== > >