Critical DNS error - 4015

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.

Make sure DNS server A record is listed in the DNS server. Or this
troubleshooting may help,

Event ID 4004Or Event ID 4015 - The DNS server has encountered a critical
error from the Active Directory. Check that the Active Directory is
functioning properly. ...
http://www.chicagotech.net/troublesh...ventid4004.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Bobson" <Bobson@discussions.microsoft.com> wrote in message
news:C2FF8F49-B0B6-4182-B748-B74F4D7C1B22@microsoft.com...
> 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.
>
>

Hi Bob,

Thank you for your response! I read the link you posted. I would like to
ask if my case fall into #1, which said " If DNS server starts and Active
Directory has not started yet and is down, DNS cannot load the zone from AD
until AD has started. "

Is it a matter? My DC got the error at the moment the DC starts up.

Hope you can help (again). Thank you so much!

Bobson


"MSNews" wrote:

> Make sure DNS server A record is listed in the DNS server. Or this
> troubleshooting may help,
>
> Event ID 4004Or Event ID 4015 - The DNS server has encountered a critical
> error from the Active Directory. Check that the Active Directory is
> functioning properly. ...
> http://www.chicagotech.net/troublesh...ventid4004.htm
>
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Bobson" <Bobson@discussions.microsoft.com> wrote in message
> news:C2FF8F49-B0B6-4182-B748-B74F4D7C1B22@microsoft.com...
> > 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.
> >
> >
>
>
>