Got a critical DNS error - ID 4015

[Bobson]

Hi all,

Hope you can help.

I got the error 4015 saying "the DNS server has ecnountered a critical error
from AD. Check AD is function properly..." on my new setup DC.

In fact, the new server has been running great without any errors. It is the
FSMO, bridgehead, GC, and DNS server. The IP DNS setting is points to itself
then follow by another DNS server which is also a DC. Rather than the AD DNS,
I also have couple other zones using the new server as primary while others
DCs as secondary.

The new server, again, does not have the error as it runs for 3 weeks
already. Last Friday I just did a DHCP migration from a old DC to this new
server (by using netsh export dhcp..." from the support tools. AFterwards, I
rebooted the server. Then the error came up.

I ran DCdiag and netdiag but no errors found.

I did some research and found that some people said it is each object of DNS
attribute value only limits to 800 only... more than that causing the error.
and SP2 will fix it... Is it true?

What cause this problem, and what is your suggestion to fix the problem? Do
you think it is worth paying some$ to call in for MS support help?

Thank you so much for your help.

[Jorge Silva]

Hi
Is this error logged at the boot process?
If no check some scenarios:
http://support.microsoft.com/kb/914036/en-us
http://support.microsoft.com/kb/267855/en-us
http://support.microsoft.com/kb/909249/en-us
http://eventid.net/display.asp?eventid=4015&eventno=333&source=DNS&phase=1
--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

Post by Bobson
Hi all,
Hope you can help.
I got the error 4015 saying "the DNS server has ecnountered a critical error
from AD. Check AD is function properly..." on my new setup DC.
In fact, the new server has been running great without any errors. It is the
FSMO, bridgehead, GC, and DNS server. The IP DNS setting is points to itself
then follow by another DNS server which is also a DC. Rather than the AD DNS,
I also have couple other zones using the new server as primary while others
DCs as secondary.
The new server, again, does not have the error as it runs for 3 weeks
already. Last Friday I just did a DHCP migration from a old DC to this new
server (by using netsh export dhcp..." from the support tools. AFterwards, I
rebooted the server. Then the error came up.
I ran DCdiag and netdiag but no errors found.
I did some research and found that some people said it is each object of DNS
attribute value only limits to 800 only... more than that causing the error.
and SP2 will fix it... Is it true?
What cause this problem, and what is your suggestion to fix the problem? Do
you think it is worth paying some$ to call in for MS support help?
Thank you so much for your help.