DNS error 4015

  • Thread starter Thread starter AJ
  • Start date Start date
A

AJ

I am getting a 4015 event log error on one of my windows
2003 domain controllers. I have two DCs on the network
single site single domain. The message is

"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 "". The event data
contains the error."

I found technet info for the event on windows 2000, but
it seems to refer to having more than 800 DC objects in
AD.

Any help in resolving this issue would greatly be
appreciated.

Thanks - Aj
 
In
AJ said:
I am getting a 4015 event log error on one of my windows
2003 domain controllers. I have two DCs on the network
single site single domain. The message is

"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 "". The event data
contains the error."

I found technet info for the event on windows 2000, but
it seems to refer to having more than 800 DC objects in
AD.

Any help in resolving this issue would greatly be
appreciated.
Click to expand...

How often does it log the 4015?
 
Hello,

There are a couple of reasons to get this error.

Did this start after applying security update 835732 (MS04-011)? Also is
this the only DNS related error, you may also be getting 4004 errors? If
so then this is probably a timing issue that was introduced as a result of
the update and will cause no functionality issues whatsoever. The logging
of this event can safely be ignored and upcoming updates should address the
logging of this event in the future.

If you are recieving other errors or you have not applied the update then
we have issues in the SRV records registered for your domain. Please
confirm that the DC's are pointing to only them selves for DNS in the
TCP/IP properties. Make sure that the host records for your DC's have the
correct IP address listed in the forward lookup zone for your domain. If
you find any record that is incorrect remove it and then run ipconfig
/flushdns and ipconfig /registerdns and stop and restart the netlogon
service on both DC's.


Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose
 
-----Original Message-----
In AJ <[email protected]> posted a question
Then Kevin replied below:

How often does it log the 4015?






.It has logged the error 3 times. One happened to be
Click to expand...
back a couple months ago the other two were logged
immediately after each of the two reboots this past
weekend.
 
Larry,
After checking the patch history, yes update 835732 had
been installed back in april. I have three of these 4015
events logged. One however, had been logged in march? The
other two were logged this past weekend immediatly after
each of the two reboots I did. I wasn't sure if this was
something to be concerned with. Thanks for the help
 
Also, you mentioned that the DCs DNS should only be
pointing to themselves. After checking, each DC has
themselves as a primary DNS server and the other as a
secondary. Is this correct?
 
That is correct. What I meant is that they need to be pointed at internal
DNS servers Only. So your setup is just fine.

Here is a very good article that goes over the most common DNS questions
for Windows 2000 and 2003.

291382 Frequently Asked Questions About Windows 2000 DNS and Windows Server
http://support.microsoft.com/?id=291382


Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
back a couple months ago the other two were logged
immediately after each of the two reboots this past
weekend.
Click to expand...
It is sometime common to get this event at start up if AD has not started
when DNS starts. Since DNS is getting the zone data from AD when DNS starts
and AD has not started you will see this event. You can ignore this event if
it is not logging the 4015s at regular intervals.
There is a KB article covering this event that says pretty much the same
thing. For some reason I cannot find it in my searches.
 
Back
Top