Error 4515 - Duplicate zone information Cep 11/26/2008 1:04:01 PM Hi, I am currently in the process of building up two new DC's to replace to older DC's on our network. I have set them up on our network to replicate, GC etc and they are quite happy. Recently I added the DNS role to both of them. Our DNS is set up on all servers as "All domain controllers in Active Directory Domain" for our company.internal zone. And our _msdcs.company.internal zone is set as "All DNS servers in Active Directory Forest". The DNS information is all stored in AD. When I stop and start the two new DCs I keep getting the 4515 warning come up, "The zone company.internal was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found in directory partition DomainDNSZones.company.internal. The DNS Server will ignore this new copy of the zone." Now I have read up a lot of articles on this but I am still not 100% clear on what actually needs to be done. One set of instructions is to delete one of the partitions for the company.internal zone using ADSI edit (something I am very cautious about doing) but doesn't specify which partition clearly enough. I am going to guess I want to delete the MicrosoftDNS copy because this is an older method of replication for Win2000 servers but as my DNS is set to "All DCs" rather then "All DNS servers" maybe this is not right? Another set says I should switch all DNS servers off except one, change its replication method to "All DNS servers in Active Directory Domain", restart the DNS service and then turn on all other DNS servers so the change replicates. Can anyone give me some clear instruction on what method to do? If I delete the MicrosoftDNS DNS partition information do I first need to set all DNS servers replication method to "All DNS servers in Domain"? We are running on 5 Win2k3 servers with one forest and one domain. The zones set up for each partitions as, ForestDNS -> _msdcs.mercia.internal DomainDNS-> company.internal, RootDNSServers MicrosoftDNS -> company.internal, RootDNSServers Cheers! -- Thanks, Cep.

Re: Error 4515 - Duplicate zone information "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com> 11/27/2008 5:45:28 AM In news:761C9495-E6B6-4A24-BEE8-778E3A8BAAEB[ at ]microsoft.com, Cep <Cep[ at ]discussions.microsoft.com> requesting assistance, typed the following: [Quoted Text] > Hi, > > I am currently in the process of building up two new DC's to replace > to > older DC's on our network. I have set them up on our network to > replicate, GC etc and they are quite happy. > > Recently I added the DNS role to both of them. Our DNS is set up on > all servers as "All domain controllers in Active Directory Domain" > for our company.internal zone. And our _msdcs.company.internal zone > is set as "All DNS servers in Active Directory Forest". > > The DNS information is all stored in AD. > > When I stop and start the two new DCs I keep getting the 4515 warning > come up, > > "The zone company.internal was previously loaded from the directory > partition MicrosoftDNS but another copy of the zone has been found in > directory partition DomainDNSZones.company.internal. The DNS Server > will ignore this new copy of the zone." > > Now I have read up a lot of articles on this but I am still not 100% > clear > on what actually needs to be done. > > One set of instructions is to delete one of the partitions for the > company.internal zone using ADSI edit (something I am very cautious > about doing) but doesn't specify which partition clearly enough. I am > going to guess I want to delete the MicrosoftDNS copy because this is > an older method of replication for Win2000 servers but as my DNS is > set to "All DCs" rather then "All DNS servers" maybe this is not > right? > > Another set says I should switch all DNS servers off except one, > change its replication method to "All DNS servers in Active Directory > Domain", restart the DNS service and then turn on all other DNS > servers so the change replicates. > > Can anyone give me some clear instruction on what method to do? > > If I delete the MicrosoftDNS DNS partition information do I first > need to > set all DNS servers replication method to "All DNS servers in Domain"? > > We are running on 5 Win2k3 servers with one forest and one domain. > > The zones set up for each partitions as, > > ForestDNS -> _msdcs.mercia.internal > DomainDNS-> company.internal, RootDNSServers > MicrosoftDNS -> company.internal, RootDNSServers > > Cheers! The easiest way to clear this up is to go into ADSI Edit, drill down the DomainNC to Services, Microsoft DNS, and delete the dupe zone. You will be able to tell immediately if it is a dupe. It will have a "CNF...." or "PRE..." suffix with a long GUID. Just delete it. I would also check the DomainDnsZones and ForestDnsZones partitions too for the same type of entries. If you see them, delete them. The problem probably occurred while both 2000 and 2003 DCs were co-existing and at least one of the 2000 DCs was still running the DNS service. When switching over to 2003, or even 2003 to 2008, you have to keep the two different replication scopes to be backward compatible until you uninstall DNS (not delete the zone from 2000). Once you've uninstalled DNS from ALL 2000 DCs, then is it safe to change the replication scope. I have more detailed instructions if you need it, but I believe you'll be ok. Post back if you would like to see them. -- Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT Microsoft Certified Trainer For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

Re: Error 4515 - Duplicate zone information Cep 11/27/2008 12:19:01 PM Hi Ace :) Thanks for the reply. I have drilled down to MicrosoftDNS under DomainNC and it contains one zone company.internal with a load of records. I could not find any prefixes with CNF or PRE as you mentioned. I also can see a RootDNSServers zone but this is completely empty. So I then thought I would check the DomainDNSZones parition and I now appear to have alongside the company.internal two other zones with DC=....In Progress and a guid with company.internal. I guess I need to delete these two zones under DomainDNSZones and then delete the MicrosoftDNS, company.internal zone from the DomainNC partition, is that right? :) -- Thanks, Cep. "Ace Fekay [Microsoft Certified Trainer]" wrote: [Quoted Text] > In news:761C9495-E6B6-4A24-BEE8-778E3A8BAAEB[ at ]microsoft.com, > Cep <Cep[ at ]discussions.microsoft.com> requesting assistance, typed the > following: > > Hi, > > > > I am currently in the process of building up two new DC's to replace > > to > > older DC's on our network. I have set them up on our network to > > replicate, GC etc and they are quite happy. > > > > Recently I added the DNS role to both of them. Our DNS is set up on > > all servers as "All domain controllers in Active Directory Domain" > > for our company.internal zone. And our _msdcs.company.internal zone > > is set as "All DNS servers in Active Directory Forest". > > > > The DNS information is all stored in AD. > > > > When I stop and start the two new DCs I keep getting the 4515 warning > > come up, > > > > "The zone company.internal was previously loaded from the directory > > partition MicrosoftDNS but another copy of the zone has been found in > > directory partition DomainDNSZones.company.internal. The DNS Server > > will ignore this new copy of the zone." > > > > Now I have read up a lot of articles on this but I am still not 100% > > clear > > on what actually needs to be done. > > > > One set of instructions is to delete one of the partitions for the > > company.internal zone using ADSI edit (something I am very cautious > > about doing) but doesn't specify which partition clearly enough. I am > > going to guess I want to delete the MicrosoftDNS copy because this is > > an older method of replication for Win2000 servers but as my DNS is > > set to "All DCs" rather then "All DNS servers" maybe this is not > > right? > > > > Another set says I should switch all DNS servers off except one, > > change its replication method to "All DNS servers in Active Directory > > Domain", restart the DNS service and then turn on all other DNS > > servers so the change replicates. > > > > Can anyone give me some clear instruction on what method to do? > > > > If I delete the MicrosoftDNS DNS partition information do I first > > need to > > set all DNS servers replication method to "All DNS servers in Domain"? > > > > We are running on 5 Win2k3 servers with one forest and one domain. > > > > The zones set up for each partitions as, > > > > ForestDNS -> _msdcs.mercia.internal > > DomainDNS-> company.internal, RootDNSServers > > MicrosoftDNS -> company.internal, RootDNSServers > > > > Cheers! > > > The easiest way to clear this up is to go into ADSI Edit, drill down the > DomainNC to Services, Microsoft DNS, and delete the dupe zone. You will be > able to tell immediately if it is a dupe. It will have a "CNF...." or > "PRE..." suffix with a long GUID. Just delete it. I would also check the > DomainDnsZones and ForestDnsZones partitions too for the same type of > entries. If you see them, delete them. > > The problem probably occurred while both 2000 and 2003 DCs were co-existing > and at least one of the 2000 DCs was still running the DNS service. When > switching over to 2003, or even 2003 to 2008, you have to keep the two > different replication scopes to be backward compatible until you uninstall > DNS (not delete the zone from 2000). Once you've uninstalled DNS from ALL > 2000 DCs, then is it safe to change the replication scope. > > I have more detailed instructions if you need it, but I believe you'll be > ok. Post back if you would like to see them. > > -- > Ace > > This posting is provided "AS-IS" with no warranties or guarantees and > confers no rights. > > Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT > Microsoft Certified Trainer > > For urgent issues, you may want to contact Microsoft PSS directly. > Please check http://support.microsoft.com for regional support phone > numbers. > >

Re: Error 4515 - Duplicate zone information "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com> 11/28/2008 2:48:07 PM In news:852BA87E-7C6B-405B-AF22-FF2785FDD2B3[ at ]microsoft.com, Cep <Cep[ at ]discussions.microsoft.com> requesting assistance, typed the following: [Quoted Text] > Hi Ace :) > > Thanks for the reply. > > I have drilled down to MicrosoftDNS under DomainNC and it contains > one zone company.internal with a load of records. I could not find > any prefixes with CNF or PRE as you mentioned. I also can see a > RootDNSServers zone but this is completely empty. > > So I then thought I would check the DomainDNSZones parition and I now > appear to have alongside the company.internal two other zones with > DC=....In Progress and a guid with company.internal. > > I guess I need to delete these two zones under DomainDNSZones and then > delete the MicrosoftDNS, company.internal zone from the DomainNC > partition, is that right? :) > Before you delete anything, good you found which partition it is in. Since the dupe, as AD sees it, is in the DomainDnsZones partition, go to all your DCs, and make sure the replication scopes are set to the Windows 2000 compatible setting (the bottom button). Let replication occur. If you have multiple sites, and AD sites configured, allow the time to replicate based on the site schedule and frequency. Once you are sure replication occured between all DCs, then go back into ADSI Edit (open a fresh console to get a refreshed view), delete the conflicting zone, NOT the partition. Now allow that to replicate. Look at it later to insure the offending zone is gone. Then go back to only ONE of your DCs, and change the scope to the middle button, which will put it in the DomainDnsZones partition. Check ADSI Edit after replication occurs to make sure all is as desired. I hope that helps. Ace

Re: Error 4515 - Duplicate zone information Cep 11/28/2008 4:39:19 PM Hi Ace, I have followed your instructions but when I reach the last point about changing the replication scope I get a really daft error coming up saying something about the name of the network device and then it fails to complete. I believe I have heard this mentioned but I don't think I have seen a fix. Do you know what this means? -- Thanks, Cep. "Ace Fekay [Microsoft Certified Trainer]" wrote: [Quoted Text] > In news:852BA87E-7C6B-405B-AF22-FF2785FDD2B3[ at ]microsoft.com, > Cep <Cep[ at ]discussions.microsoft.com> requesting assistance, typed the > following: > > Hi Ace :) > > > > Thanks for the reply. > > > > I have drilled down to MicrosoftDNS under DomainNC and it contains > > one zone company.internal with a load of records. I could not find > > any prefixes with CNF or PRE as you mentioned. I also can see a > > RootDNSServers zone but this is completely empty. > > > > So I then thought I would check the DomainDNSZones parition and I now > > appear to have alongside the company.internal two other zones with > > DC=....In Progress and a guid with company.internal. > > > > I guess I need to delete these two zones under DomainDNSZones and then > > delete the MicrosoftDNS, company.internal zone from the DomainNC > > partition, is that right? :) > > > > Before you delete anything, good you found which partition it is in. Since > the dupe, as AD sees it, is in the DomainDnsZones partition, go to all your > DCs, and make sure the replication scopes are set to the Windows 2000 > compatible setting (the bottom button). Let replication occur. If you have > multiple sites, and AD sites configured, allow the time to replicate based > on the site schedule and frequency. Once you are sure replication occured > between all DCs, then go back into ADSI Edit (open a fresh console to get a > refreshed view), delete the conflicting zone, NOT the partition. Now allow > that to replicate. Look at it later to insure the offending zone is gone. > Then go back to only ONE of your DCs, and change the scope to the middle > button, which will put it in the DomainDnsZones partition. Check ADSI Edit > after replication occurs to make sure all is as desired. > > I hope that helps. > > Ace > >

Re: Error 4515 - Duplicate zone information "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com> 12/2/2008 3:29:57 AM In news:566F9F29-7F8F-40FD-9439-71B037EAFC33[ at ]microsoft.com, Cep <Cep[ at ]discussions.microsoft.com> requesting assistance, typed the following: [Quoted Text] > Hi Ace, > > I have followed your instructions but when I reach the last point > about changing the replication scope I get a really daft error coming > up saying something about the name of the network device and then it > fails to complete. I believe I have heard this mentioned but I don't > think I have seen a fix. > > Do you know what this means? > Sounds like you may have had a replication issue at one point as well. It could have been caused by this, it may not have been caused by this. Either way, the error, even though it doesn't make sense, is due to the dupe. The following is a copy/paste from my blog at www.fekay.com showing the full method to clean it all up. It involves picking one DC (only one), and removing the zone from AD (make it no AD integrated), so it is now a Primary Standard zone. Then allow replication to happen. Then do the ADSI Edit deletions, but this time delete ALL references to the zone (not the ForestDnsZones, just the zones in DomainNC and DomainDnsZones). ================================== ================================== Conflicting AD Integrated zones if they exist in both the Domain NC and one of the Application Partitions or if you get a weird error message stating: "The name limit for the local computer network adapter card was exceeded." Under Windows 2000, the physcial AD database is broken up into 3 logical partitions, the DomainNC (Domain Name Context, or some call the Domain Name Container), the Configuration Partition, and the Schema Partition. The Schema and Config partitions replicate to all DCs in a forest. However, the DomainNC is specific only to the domain the DC belongs to. That's where a user, domain local or global group is stored. The DomainNC only replicates to the DCs of that specific domain. When you create an AD INtegrated zone in Win 2000, it gets stored in the DomainNC. This causes a limitation if you want this zone to be available on a DC/DNS server that belongs to a different domain. The only way to get around that is for a little creative designing using either delegation, or secondary zones. This was a challenge for the _msdcs zone, which must be available forest wide to resolve the forest root domain, which contains the Schema and Domain Name Masters FSMO roles. In Windows 2003, there were two additional partitions added, they are called the DomainDnsZones and ForestDnsZones Application Partitions, specifically to store DNS data. They were conceived to overcome the limitation of Windows 2000's AD Integrated zones. Now you can store an AD Integrated zone in either of these new partitions instead of the DomainNC. If stored in the DomainDnsZones app partition, it is available only in that domain's DomainDnsZones partition. If you store it in the ForestDnsZones app partition, it will be available to any DC/DNS server in the whole forest. This opens many more design options. It also ensures the availability of the _msdcs zone to all DCs in the forest. By default in Win 2003, the _msdcs zone is stored in the ForestDnsZones application partition. When selecting a zone replication scope in Win2003, in the zone's properties, click on the "Change" button. Under that you will see 3 options: To choose the ForestDnsZones: "To all DNS servers in the AD forest example.com" To choose DomainDnsZones: "To all DNS servers in the AD domain example.com" To choose the DomainNC (only for compatibility with Win2000): "To all domain controllers in the AD domain example.com" If you have a duplicate, that's indicating there is a zone that exists in the DomainNC and in the DomainDnsZones Application partition. This means at one time, or currently, you have a mixed Win2000/2003 environment and you have DNS installed on both operating systems. On Win2000, if the zone is AD Integrated, it is in the DomainNC, and should be set the same in Win2003's DC/DNS server to keep compatible. Someone must have attempted to change it in Win2003 DNS to put it in the DomainDnsZones partition no realizing the implications, hence the duplicate. In a scenario such as this where you want to use the Win2003 app partitions, you then must insure the zone on the Win2003 is set to the DomainNC, then uninstall DNS off the Win2000 machine, then once that's done, you can then go to the Win2003 DNS and change the partition's replication scope to one of the app partitions. In ADSI Edit, you can view all five partitions. You were viewing the app partitions, but not the main partitions. You need to add the DomainNC partition in order to delete that zone. But you must uninstall DNS off the Win2000 server first, unless you want to keep the zone in the DomainNC. But that wouldn't make much sense if you want to take advantage of the _msdcs zone being available forest wide in the ForestDnsZones partition, which you should absolutley NOT delete. I would just use the Win2003 DNS servers only. In ADSI Edit, rt-click ADSI Edit, connect to, in the Connection Point click on "Well known Naming Context", then in the drop-down box, select "Domain". Drill down to CN=System. Under that you will see CN=MicrosoftDNS. You will see the zone in there. But make sure to decide FIRST which way to go before you delete anything. Some reading for you... Directory Partitions: http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/distrib/dsbg_dat_favt.asp kbAlertz- (867464) - Explains how to use ADSI Edit to resolve app partitions issues: http://www.kbalertz.com/kb_867464.aspx How to fix it? ------------- What I've done in a few cases with my clients that have issues with 'duplicate' zone entries in AD (because the zone name was in the Domain NC (Name Container) Partition, and also in the DomainDnsZones App partition), was first to change the zone on one of the DCs to a Primary zone, and allowed zone transfers. Then I went to the other DCs and changed the zone to a Secondary, and using the first DC as the Master. Then I went into ADSI Edit, (from memory) under the Domain NC, Services, DNS, and deleted any reference to the domain name. Then I added the DomainDnsZones partition to the ADSI Edit console, and deleted any reference to the zone name in there as well. If you see anything saying something to the extent of a phrase that says "In Progress...." or "CNF" with a long GUID number after it, delete them too. Everytime you may have tried tochange the replication scope, it creates one of them. Delete them all. Then I forced replication. If there were Sites configured, I juggled around the servers and subnet objects so all of the servers are now in one site, then I forced replication (so I didn't have to wait for the next site replication schedule). Once I've confirmed that replication occured, and the zones no longer existed in either the Domain NC or DomainDnsZones, then I changed the zone on the first server back to AD Integrated, choosing the middle button for it's replication scope (which puts it in the DomainDnsZones app partition). Then I went to the other servers and changed the zone to AD Integrated choosing the same replication scope. Then I reset the sites and subnet objects, and everything was good to go. Keep in mind, I left the _msdcs... zone alone, since that wasn't causing any problems and is located in the ForestDnsZones (default) in all of my client cases I've come across with so far. It seems like alot of steps, but not really. Just read it over a few times to get familiar with the procedure. You may even want to change it into a numbered step by step list if you like. If you only have one DC, and one Site, then it's much easier since you don't have to mess with secondaries or play with the site objects. I hope that helped! ================================== ================================== -- Ace\

Re: Error 4515 - Duplicate zone information Cep 12/5/2008 11:32:00 AM Hi Ace, Sorry for the late reply, I've been on First Aid training and a conference this week! Anyway I have read through your steps and I believe for me this would be, 1. In DNS Manager select the Forward lookup zones tree node 2. Expand company.internal zone tree node 3. Right click company.internal node and select properties 4. Change Type to primary if not already set and remove the checkbox from store in active directory. 5. Apply ok, exit DNS manager 6. Go to every other DC/DNS server, repeating steps 1 to 5, except at step 4 set to secondary zone not primary. 7. On the primary DNS zone server, open ADSI edit 8. Expand the DC=company, DC=internal tree node, drill down to System-> MicrosoftDNS 9. Delete all company.internal zones 10. Expand the DC=DomainDNSZones, DC=company, DC=internal tree node, drill down to MicrosoftDNS 11. Delete all company.internal zones 12. Force replication from AD Sites and Services 13. Check on each DC/DNS server that the replication has taken place 14. Go back to primary DC/DNS server and switch back to AD integrated through DNS manager 15. Set replication to middle option All DNS servers in Domain 16. Go back to each DC/DNS server and set them back to AD Integrated, and the same replication scope.* 17.Check everything is good. *At point 16 do I make all these secondary zones, primary's once more? Is there anything here I am missing or anything else I should be wary of? Cheers -- Thanks, Cep. "Ace Fekay [Microsoft Certified Trainer]" wrote: [Quoted Text] > In news:566F9F29-7F8F-40FD-9439-71B037EAFC33[ at ]microsoft.com, > Cep <Cep[ at ]discussions.microsoft.com> requesting assistance, typed the > following: > > Hi Ace, > > > > I have followed your instructions but when I reach the last point > > about changing the replication scope I get a really daft error coming > > up saying something about the name of the network device and then it > > fails to complete. I believe I have heard this mentioned but I don't > > think I have seen a fix. > > > > Do you know what this means? > > > Sounds like you may have had a replication issue at one point as well. It > could have been caused by this, it may not have been caused by this. Either > way, the error, even though it doesn't make sense, is due to the dupe. The > following is a copy/paste from my blog at www.fekay.com showing the full > method to clean it all up. It involves picking one DC (only one), and > removing the zone from AD (make it no AD integrated), so it is now a Primary > Standard zone. Then allow replication to happen. Then do the ADSI Edit > deletions, but this time delete ALL references to the zone (not the > ForestDnsZones, just the zones in DomainNC and DomainDnsZones). > > ================================== > ================================== > > Conflicting AD Integrated zones if they exist in both the Domain NC and > one of the Application Partitions or if you get a weird error message > stating: > "The name limit for the local computer network adapter card was exceeded." > > Under Windows 2000, the physcial AD database is broken up into 3 logical > partitions, the DomainNC (Domain Name Context, or some call the Domain Name > Container), the Configuration Partition, and the Schema Partition. The > Schema and Config partitions replicate to all DCs in a forest. However, the > DomainNC is specific only to the domain the DC belongs to. That's where a > user, domain local or global group is stored. The DomainNC only replicates > to the DCs of that specific domain. When you create an AD INtegrated zone in > Win 2000, it gets stored in the DomainNC. This causes a limitation if you > want this zone to be available on a DC/DNS server that belongs to a > different domain. The only way to get around that is for a little creative > designing using either delegation, or secondary zones. This was a challenge > for the _msdcs zone, which must be available forest wide to resolve the > forest root domain, which contains the Schema and Domain Name Masters FSMO > roles. > > In Windows 2003, there were two additional partitions added, they are called > the DomainDnsZones and ForestDnsZones Application Partitions, specifically > to store DNS data. They were conceived to overcome the limitation of Windows > 2000's AD Integrated zones. Now you can store an AD Integrated zone in > either of these new partitions instead of the DomainNC. If stored in the > DomainDnsZones app partition, it is available only in that domain's > DomainDnsZones partition. If you store it in the ForestDnsZones app > partition, it will be available to any DC/DNS server in the whole forest. > This opens many more design options. It also ensures the availability of the > _msdcs zone to all DCs in the forest. By default in Win 2003, the _msdcs > zone is stored in the ForestDnsZones application partition. > > When selecting a zone replication scope in Win2003, in the zone's > properties, click on the "Change" button. Under that you will see 3 options: > To choose the ForestDnsZones: > "To all DNS servers in the AD forest example.com" > > To choose DomainDnsZones: > "To all DNS servers in the AD domain example.com" > > To choose the DomainNC (only for compatibility with Win2000): > "To all domain controllers in the AD domain example.com" > > > If you have a duplicate, that's indicating there is a zone that exists in > the DomainNC and in the DomainDnsZones Application partition. This means at > one time, or currently, you have a mixed Win2000/2003 environment and you > have DNS installed on both operating systems. On Win2000, if the zone is AD > Integrated, it is in the DomainNC, and should be set the same in Win2003's > DC/DNS server to keep compatible. Someone must have attempted to change it > in Win2003 DNS to put it in the DomainDnsZones partition no realizing the > implications, hence the duplicate. In a scenario such as this where you want > to use the Win2003 app partitions, you then must insure the zone on the > Win2003 is set to the DomainNC, then uninstall DNS off the Win2000 machine, > then once that's done, you can then go to the Win2003 DNS and change the > partition's replication scope to one of the app partitions. > > In ADSI Edit, you can view all five partitions. You were viewing the app > partitions, but not the main partitions. You need to add the DomainNC > partition in order to delete that zone. But you must uninstall DNS off the > Win2000 server first, unless you want to keep the zone in the DomainNC. But > that wouldn't make much sense if you want to take advantage of the _msdcs > zone being available forest wide in the ForestDnsZones partition, which you > should absolutley NOT delete. I would just use the Win2003 DNS servers only. > > In ADSI Edit, rt-click ADSI Edit, connect to, in the Connection Point click > on "Well known Naming Context", then in the drop-down box, select "Domain". > Drill down to CN=System. Under that you will see CN=MicrosoftDNS. You will > see the zone in there. > > But make sure to decide FIRST which way to go before you delete anything. > > Some reading for you... > Directory Partitions: > http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/distrib/dsbg_dat_favt.asp > > kbAlertz- (867464) - Explains how to use ADSI Edit to resolve app partitions > issues: > http://www.kbalertz.com/kb_867464.aspx > > > How to fix it? > ------------- > > What I've done in a few cases with my clients that have issues with > 'duplicate' zone entries in AD (because the zone name was in the Domain NC > (Name Container) Partition, and also in the DomainDnsZones App partition), > was first to change the zone on one of the DCs to a Primary zone, and > allowed zone transfers. Then I went to the other DCs and changed the zone to > a Secondary, and using the first DC as the Master. Then I went into ADSI > Edit, (from memory) under the Domain NC, Services, DNS, and deleted any > reference to the domain name. Then I added the DomainDnsZones partition to > the ADSI Edit console, and deleted any reference to the zone name in there > as well. If you see anything saying something to the extent of a phrase that > says > "In Progress...." or "CNF" with a long GUID number after it, delete them > too. Everytime > you may have tried tochange the replication scope, it creates one of them. > Delete them all. > > Then I forced replication. If there were Sites configured, I juggled around > the servers and subnet objects so all of the servers are now in one site, > then I forced replication (so I didn't have to wait for the next site > replication schedule). Once I've confirmed that replication occured, and the > zones no longer existed in either the Domain NC or DomainDnsZones, then I > changed the zone on the first server back to AD Integrated, choosing the > middle button for it's replication scope (which puts it in the > DomainDnsZones app partition). Then I went to the other servers and changed > the zone to AD Integrated choosing the same replication scope. Then I reset > the sites and subnet objects, and everything was good to go. > > Keep in mind, I left the _msdcs... zone alone, since that wasn't causing any > problems and is located in the ForestDnsZones (default) in all of my client > cases I've come across with so far. > > It seems like alot of steps, but not really. Just read it over a few times > to get familiar with the procedure. You may even want to change it into a > numbered step by step list if you like. If you only have one DC, and one > Site, then it's much easier since you don't have to mess with secondaries or > play with the site objects. > > I hope that helped! > > ================================== > ================================== > -- > Ace\ > >

Re: Error 4515 - Duplicate zone information "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com> 12/7/2008 4:26:03 AM In news:E20E9A3B-EBE4-4BFE-B1D6-DF8BC57EB128[ at ]microsoft.com, Cep <Cep[ at ]discussions.microsoft.com> requesting assistance, typed the following: [Quoted Text] > Hi Ace, > > Sorry for the late reply, I've been on First Aid training and a > conference this week! > > Anyway I have read through your steps and I believe for me this would > be, > > 1. In DNS Manager select the Forward lookup zones tree node > 2. Expand company.internal zone tree node > 3. Right click company.internal node and select properties > 4. Change Type to primary if not already set and remove the checkbox > from store in active directory. > 5. Apply ok, exit DNS manager > 6. Go to every other DC/DNS server, repeating steps 1 to 5, except at > step 4 set to secondary zone not primary. > 7. On the primary DNS zone server, open ADSI edit > 8. Expand the DC=company, DC=internal tree node, drill down to > System-> MicrosoftDNS > 9. Delete all company.internal zones > 10. Expand the DC=DomainDNSZones, DC=company, DC=internal tree node, > drill down to MicrosoftDNS > 11. Delete all company.internal zones > 12. Force replication from AD Sites and Services > 13. Check on each DC/DNS server that the replication has taken place > 14. Go back to primary DC/DNS server and switch back to AD integrated > through DNS manager > 15. Set replication to middle option All DNS servers in Domain > 16. Go back to each DC/DNS server and set them back to AD Integrated, > and the same replication scope.* > 17.Check everything is good. > > *At point 16 do I make all these secondary zones, primary's once more? > > Is there anything here I am missing or anything else I should be wary > of? > > Cheers Changes to your steps: Step 5: Just hit apply and leave the MMC open. Step 6: Eliminate your step # 6. As I said, only pick ONE DC to do this on. Once it is removed from AD, all the others will reflect that change through AD replication. Remember, anything to do with or changes made in AD on one machine, is replicated to ALL in the domain or forest (depending on the type of change). That was why I said pick one DC. Step 7: This can be done from ANY domain controller or workstation provided the adminpak tools are installed and you are logged in as an enterprise admin. Step 9 & 11: Don't forget to delete anything zone you see with a prefix of "CNF...." or "PRE..." and some long GUID after it. These are the actual duplicate zones AD found. Step 14: Go back to the original DC that you changed the zone to a non-AD Integrated zone to do this. Just an FYI, there really is no such thing as a "Primary DC" in AD as there was in Windows NT4. All DCs in AD are replicas. Now if you meant to go back to the DC that now holds the Primary Standard Zone that you changed, I apologize for the misunderstanding. Let me know how you make out! Ace

Re: Error 4515 - Duplicate zone information Cep 12/9/2008 4:49:02 PM Hi Ace, Yep your right I did mean primary zone, not PDC. I did make a few other steps in addition to the ones we discussed which were to add a new machine to the network and test to see where the DNS record was created first. After this I powered down two DCs and kept them on the sidelines in case things went horribly wrong. After the duplicate zone was deleted in DomainDNSZones (not DomainDC afterall!) I tried restarting DNS, got no more errors. Allowed the others to boot up and then replicate. Once they had I changed the scope and its all good! Thank you ever so much for all your help Ace, you are a star! -- Thanks, Cep. "Ace Fekay [Microsoft Certified Trainer]" wrote: [Quoted Text] > In news:E20E9A3B-EBE4-4BFE-B1D6-DF8BC57EB128[ at ]microsoft.com, > Cep <Cep[ at ]discussions.microsoft.com> requesting assistance, typed the > following: > > Hi Ace, > > > > Sorry for the late reply, I've been on First Aid training and a > > conference this week! > > > > Anyway I have read through your steps and I believe for me this would > > be, > > > > 1. In DNS Manager select the Forward lookup zones tree node > > 2. Expand company.internal zone tree node > > 3. Right click company.internal node and select properties > > 4. Change Type to primary if not already set and remove the checkbox > > from store in active directory. > > 5. Apply ok, exit DNS manager > > 6. Go to every other DC/DNS server, repeating steps 1 to 5, except at > > step 4 set to secondary zone not primary. > > 7. On the primary DNS zone server, open ADSI edit > > 8. Expand the DC=company, DC=internal tree node, drill down to > > System-> MicrosoftDNS > > 9. Delete all company.internal zones > > 10. Expand the DC=DomainDNSZones, DC=company, DC=internal tree node, > > drill down to MicrosoftDNS > > 11. Delete all company.internal zones > > 12. Force replication from AD Sites and Services > > 13. Check on each DC/DNS server that the replication has taken place > > 14. Go back to primary DC/DNS server and switch back to AD integrated > > through DNS manager > > 15. Set replication to middle option All DNS servers in Domain > > 16. Go back to each DC/DNS server and set them back to AD Integrated, > > and the same replication scope.* > > 17.Check everything is good. > > > > *At point 16 do I make all these secondary zones, primary's once more? > > > > Is there anything here I am missing or anything else I should be wary > > of? > > > > Cheers > > Changes to your steps: > > Step 5: Just hit apply and leave the MMC open. > > Step 6: Eliminate your step # 6. As I said, only pick ONE DC to do this on. > Once it is removed from AD, all the others will reflect that change through > AD replication. Remember, anything to do with or changes made in AD on one > machine, is replicated to ALL in the domain or forest (depending on the type > of change). That was why I said pick one DC. > > Step 7: This can be done from ANY domain controller or workstation provided > the adminpak tools are installed and you are logged in as an enterprise > admin. > > Step 9 & 11: Don't forget to delete anything zone you see with a prefix of > "CNF...." or "PRE..." and some long GUID after it. These are the actual > duplicate zones AD found. > > Step 14: Go back to the original DC that you changed the zone to a non-AD > Integrated zone to do this. Just an FYI, there really is no such thing as a > "Primary DC" in AD as there was in Windows NT4. All DCs in AD are replicas. > Now if you meant to go back to the DC that now holds the Primary Standard > Zone that you changed, I apologize for the misunderstanding. > > Let me know how you make out! > > Ace > > > >

Re: Error 4515 - Duplicate zone information "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname[ at ]hotmail.com> 12/11/2008 6:47:18 AM In news:82778B3B-AA5B-4231-A81F-ABE5CCAE0AFD[ at ]microsoft.com, Cep <Cep[ at ]discussions.microsoft.com> requesting assistance, typed the following: [Quoted Text] > Hi Ace, > > Yep your right I did mean primary zone, not PDC. I did make a few > other steps in addition to the ones we discussed which were to add a > new machine to the network and test to see where the DNS record was > created first. After this I powered down two DCs and kept them on the > sidelines in case things went horribly wrong. > > After the duplicate zone was deleted in DomainDNSZones (not DomainDC > afterall!) I tried restarting DNS, got no more errors. Allowed the > others to boot up and then replicate. Once they had I changed the > scope and its all good! > > Thank you ever so much for all your help Ace, you are a star! No problem and glad I was able to help, Cep. My pleasure! Thanks for the plug. We're all out here to help and share the knowldge. Cheers! Ace