Event Error 4515
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: event id 4515 server 2008 r2 Event ID 4515, DNS warning Windows Server > Directory Services Question
Event Id 4515 Dns Server 2012
0 Sign in to vote I am getting the following DNS warning in my Windows 2008 AD. event id 4515 is logged in the dns server log in windows server 2008 should I be worried abt it ? The zone GVM.LOCAL was previously loaded from the directory partition MicrosoftDNS but another copy of the zone has been found
Adsiedit Forestdnszones
in directory partition ForestDnsZones.GVM.LOCAL. 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 domaindnszones 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. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Tuesday, February 19, 2013 2:53 AM Reply | Quote Answers 0 Sign in to vote Hi This seems to be know issue and Microsoft has released KB 867464 for same issue Event ID 4515 is logged in the DNS Server log http://support.microsoft.com/kb/867464 Event ID 4515 — DNS Server Active Directory Integration http://technet.microsoft.com/en-us/library/cc735755(v=ws.10).aspx Though it states applicable to 2003 but it surely applies to 2008 too Hope it helps ___________
you start the DNS Service Source: DNS Type: Warning Event ID: 4515 MicrosoftDNS but another copy of the zone has been found
Event Id 4015
in directory partition DomainDnsZones.Domain.local. The DNS Server will ignore this new copy of
_msdcs
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 https://social.technet.microsoft.com/Forums/windows/en-US/fb6f6d0f-e3fc-4a39-8573-26cefc8e6395/event-id-4515-dns-warning?forum=winserverDS 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. Some online searching led me to the Microsoft Knowledgebase article here. In my case the following steps resolved the http://www.jeremyroe.net/resolving-dns-event-id-4515-duplicate-dns-zones/ issue: First I started with Option 1: For Option 1: [ForestDNSZones] 1. Click Start, click Run, type adsiedit.msc, and then click OK. 2. In the console tree, right-click ADSI Edit, and then click Connect to. 3. Click Select or type a Distinguished Name or Naming Context, type the following text in the list, and then click OK:
DC=ForestDNSZones, DC=contoso, DC=com 4. In the console tree, double-click DC=ForestDNSZones, DC=contoso, DC=com. 5. Double-click CN=MicrosoftDNS, and click the zone (contoso.com). You should now be able to view the DNS records which exist in this DNS partition. If you desire to remove this partition, right-click on contoso.com and then click Delete. Note Deleting a zone is a destructive operation. Please confirm that a duplicate zone exists before you perform a deletion. 6. If you have deleted a zone, restart the DNS service. To do this, follow these steps: a. Click Start, point to All Programs, point to Administrative Tools, and then click DNS. b. In the console tree, right-click contoso.com, point to All Tasks, and then click Restart. I was able to verify the DNS Zone existed there like theStart here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and http://serverfault.com/questions/219578/duplicate-dns-zones-error-4515-in-event-log policies of this site About Us Learn more about Stack Overflow the http://www.eventid.net/display-eventid-4515-source-DNS-eventno-3593-phase-1.htm company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can event id ask a question Anybody can answer The best answers are voted up and rise to the top Duplicate DNS Zones (Error 4515 in Event Log ) up vote 2 down vote favorite 1 I am getting these two error in the DNS Event log (errors at end of question). I have confirmed I do have duplicate zones. I am wondering which ones event id 4515 to delete. The DomainDNSZone contains all of our DNS records but it does not have the _msdcs zone.... that is in the ForestDNSZone with the duplicates that are not in use. 3 Questions. I understand the advantages of having DNS in the ForestDNSZone. so... Why is DNS using the DomainDNSZone and is that acceptable considering _msdcs... is in the ForestDNSZone? If so, should I just delete the DC=1.168.192.in-addr.arpa and DC=supernova.local from the ForestDNSZone? Or should I try to get those to be the ones in use? What are those steps? I understand how to delete. That is simple but if i must move zones some info would be appreaciated there. Just to confirm. from my understanding. I can delete the two duplicates in the ForestDNSZone and leave the _msdcs.supernova.local as thats required there. This will resolve the erros I see. Just fyi when I look in those folders from the ForestDNSZone they have just 2 and 1 entries respectively. So obviously not in use compared to the others. I am pretty sure I understand the steps to complete this. But if you would li
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 4515 Source: DNS Source: DNS Type: Warning Description:The zone