Getting Event ID error 4015 and 4004

your problem is that active directory is not working  so that DNS  or exchange servers can't read from the active directory
just it
restart the server and everything will be fine
kind regards
mcse+ security

I did restart twice and the problem was not fixed.

Details
Product: Windows Operating System
Event ID: 4004
Source: DNS
Version: 5.2
Symbolic Name: DNS_EVENT_DS_ZONE_ENUM_FAILED
Message: The DNS server was unable to complete directory service enumeration of zone %1. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "%2". The event data contains the error.
   
Explanation
The DNS Server service uses Active Directory to store DNS data, and it encountered a Lightweight Directory Access Protocol (LDAP) error while querying the directory. This error could be caused by either a high load on the domain controller or the failure of other domain controller services.
 
   
User Action
If this message appears repeatedly, restart the DNS Server service, and then look in the event log for other events occurring at the same time that could be causing this problem.
 
 

Product: Windows Operating System
Event ID: 4015
Source: DNS
Version: 5.2
Symbolic Name: DNS_EVENT_DS_INTERFACE_ERROR
Message: The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "%1". The event data contains the error.
   
Explanation
The DNS Server service uses Active Directory to store DNS data, and it encountered a Lightweight Directory Access Protocol (LDAP) error while querying the directory. This error could be caused by either a time-out or a temporary interruption of service.
 
   
User Action
If this message appears repeatedly, restart the DNS Server service.

For more information about DNS and DNS troubleshooting procedures, see Domain Name System(DNS)Center.
 
FROM MICROSOFT WIBESITE

I did try that and I am still getting the error.  In the event viewer, under DNS, the log are filled with ID 4015 and 4004.

IS THERE ANY LOG EVENTS  OCCURS AT THE SAME TIME

When I restart the DNS service, I am getting error 4015 and 4004 error right away.  There does not seems to have any other error that occur at the same time.

This is the error I am getting when running DCdiag:

C:\Documents and Settings\pctech>dcdiag

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Montreal\server03
      Starting test: Connectivity
         The host 828b4244-1eb5-488b-a014-aad182b88d78._msdcs.domain.local could
 not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (828b4244-1eb5-488b-a014-aad182b88d78._msdcs.domain.local) couldn't be
         resolved, the server name (server03.domain.local) resolved to the IP
         address (192.168.42.3) and was pingable.  Check that the IP address is
         registered correctly with the DNS server.
         ......................... server03 failed test Connectivity

Doing primary tests

   Testing server: Montreal\server03
      Skipping all tests, because server server03 is
      not responding to directory service requests

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : domain
      Starting test: CrossRefValidation
         ......................... domain passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... domain passed test CheckSDRefDom

   Running enterprise tests on : domain.local
      Starting test: Intersite
         ......................... domain.local passed test Intersite
      Starting test: FsmoCheck
         ......................... domain.local passed test FsmoCheck

Regards,

CHECK SERVER 3  tcp/ip configuration and ensure that it has the right ip address and  ensure that it point to your  dns server as the prefered dns server
regards

I double check this and all is properly configured.

Regards,

is  the  tcp/ip is provied by dhcp or manually
if  provided by dhcp  configure  change it to manually configuration
and my last try is to make sure that server 3 have a a   srv record at the dns lookup zone

The IP address is setup manually.  And as I stated, in my initial post, the forward lookup zone is not working, getting a red X with error: Zone not loaded by DNS server.

Regards,

If you have installed AD using Dcprom , the dcpromo create the .(root) zone and when you need to use the forwords option as Microsoft recommendation for Internet names resolution you will always get the 4004 & 4015 errors in your log. To solve this problem and stop these events do the following:
1. Create a .(root) zone file
2. Right click the .(root) name and select Properties
3. Change the zone into a primary zone instead of the integrated AD zone type
4. Delete the .(root) zone

Keep in mind that DNS are not my field of expertise.  Where do I create the .root zone file, does it matter?

I have only 1 DNS server and only one primary zone define.  When I go in the property of the primary zone, it says Expired???  How can this be with a primary zone???

Regards,

My site is down right now because of this.  Anyone?

When I try to delete the zone I am getting this error:

The zone cannot be deleted.  The active Directory service is not available.

I need help.  My site is down since this morning.  

Upon seeing these two errors together, it is usually the result of a misconfigured multihomed server.

Do you have multiple NICs on this server?

Another thing you should try is this:

go to the server's command prompt and type:

Net stop Netlogon
Net start netlogon
Ipconfig /flushDNS

Therer is only 1 nic on the server.  I also try to start and stop the Netlogon.  Still no go.  The same is true with IPconfig /flushdns.

I also try to delete the nic card and recreate it.  The server is running under Vmware ESX 3.5.  There are about 80 mailbox on the server.  

I cannot do anything with the forward lookup zone.  I had the assistance of a consultant who is an expert.  He also could not found the problem.  We open a case at Microsoft and they told us that they never seen this before.  They are still working on it.  

Really not sure what to do next.  The site as been down all day.  Not looking good for tomorrow.

Regards,

I have also seen this when IPver 6 was on the server and DNS was not configured to handle IPv6.

I am going to provide you a link. Please evaluate your system to determine if you have IP version 6 enabled. If so, stop and get back in touch with me. We will evaluate if your LAN can support IPv6, and if you wish to use IPv6.

http://beta.experts-exchange.com/questions/23604907/DNS-resolution-issues.html

If you are NOT running IPv6 and have determined the above solution is not your solution:

Then, let's look at a couple more solutions I was working on that resolved the issues of events 4004 and 4015.

____________________________________________________________
Errors 4015 and 4004 can usually be ignored if these events happen upon startup:

It means DNS was started before AD service. They will go away if this was upon loadup. I just helped someone with these errors.

https://www.experts-exchange.com/questions/22901131/THE-DNS-server-has-encountered-a-critical-error-from-the-Active-Directory.html
_____________________________________________________________________
If the problem goes unresolved, you may wish to look in your reverse lookup zone, and also check the DHCP service on bot the servers and clients to make sure they are enabled. The below article may help you.

https://www.experts-exchange.com/questions/21213433/EVENT-ID-4004-4015.html
________________________________________________________________________________

If DHCP client is running and these events continue beyond startup, then look at your reverse lookup zone records for your DC.

Your clients will look at their preferred DNS server IPs, it will go to the reverse lookup zone and try to determine a name for your AD servers. If there is no reverse zone lookup for  your DC, or there is an error in the reverse lookup zone, then you could see these errors you describe.

Guess that will do it too. Glad to see you got it fixed.

i have the same problem.  how did you fix the corrupted database?