localzuk Posted January 12, 2015 Posted January 12, 2015 I am currently trying to tidy up some errors that have appeared on our servers. Namely, on our 2012 DNS server I am seeing the following: Log Name: DNS Server Source: Microsoft-Windows-DNS-Server-Service Date: 12/01/2015 09:19:47 Event ID: 4515 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: Server.domain.com Description: The zone _msdcs.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. If an administrator has moved this zone from one directory partition to another this may be a harmless transient condition. In this case, no action is necessary. The deletion of the original copy of the zone should soon replicate to this server. If there are two copies of this zone in two different directory partitions but this is not a transient caused by a zone move operation then one of these copies should be deleted as soon as possible to resolve this conflict. To change the replication scope of an application directory partition containing DNS zones and for more details on storing DNS zones in the application directory partitions, please see Help and Support. I've had a bit of a search around for a fix, but the only real advice I've seen seems rather drastic - disable DNS on all servers but this one, disable AD integration, restart DNS server, then restore AD integration (setting replication scope), then force replication to other servers. Is there anything less drastic that'll fix this?
Mr_Jiminy Posted January 12, 2015 Posted January 12, 2015 Is it not just the DNS service you need to restart, instead of the actual server?
localzuk Posted January 12, 2015 Author Posted January 12, 2015 Don't think so! The zone is still duplicated, regardless of restarting the DNS service. Its after a restart I noticed these messages. Also, just checked my other DNS server and it has the same messages.
Mr_Jiminy Posted January 12, 2015 Posted January 12, 2015 Coming up stumps with this, other than a recommendation to check the corresponding dates on the said records. Help with Windows DNS Event ID 4515
localzuk Posted January 12, 2015 Author Posted January 12, 2015 Hmm... Looks like I'll be needing to do some out of hours work then. The "disable everything but one" option appears to be the only way.
Muz Posted January 15, 2015 Posted January 15, 2015 These videos will help with general understanding of DNS, it's well worth the watch
Ric_ Posted January 15, 2015 Posted January 15, 2015 @localzuk I've seen that before... unfortunately, I believe that is the only way to fix it. I think it can come about due to the zone being changed in two places at once (possibly due to DNS being screwed on a DC). It may be wise to demote all bar one DCs (after backing up a lot) and re-promoting them.
localzuk Posted January 15, 2015 Author Posted January 15, 2015 That's my plan at the moment @Ric_. Things seem to be ticking over ok with the problem so I'm going to do it during the next half term. Difficult to do stuff during term time!
Mr_Jiminy Posted January 16, 2015 Posted January 16, 2015 @localzuk I've seen that before... unfortunately, I believe that is the only way to fix it. I think it can come about due to the zone being changed in two places at once (possibly due to DNS being screwed on a DC). It may be wise to demote all bar one DCs (after backing up a lot) and re-promoting them. A bad migration can also be the cause, although I'm not sure if that applies in this case.
localzuk Posted January 23, 2015 Author Posted January 23, 2015 Well, I've been through and fixed this now. Fix was: Disable DNS on all but one server. Disable Active Directory Integration on the problem zones Reboot server Re-enable AD integration. Re-enable other DNS servers. Extra zone info has disappeared, servers syncing ok, error 4515 gone.
Jkfortyseven Posted May 13, 2016 Posted May 13, 2016 Hey mate, Newbie here, would you take me through the process on more depth? Got this happening on a single 2012 DC. Appreciate your time. JK
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now