DNS server error

[JL Adamson]

Every time my server starts up, I get a 4010 error message in my event viewer
that says:

dns server was unable to create a resource record ..... The active directory
definition of this resource record is corrupt or contains an invalid DNS
name.
I've looked online but cannot find anything helpful about this particular
message. Does anyone know how to fix it? It doesn't seem to be a major
problem yet and the DNS seems to be working fine but I don't want to take any
chances.

[WLW]

The Microsoft Help and Support article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;842006 reports the
following:

MessageId=4010
Severity=Error
SymbolicName=DNS_EVENT_DS_RECORD_LOAD_FAILED

The DNS server was unable to load a resource record (RR) from the directory
at %1 in zone %2. Use the DNS console to recreate this RR or check that the
Active Directory is functioning properly and reload the zone. The event data
contains the error.

It is not a specific "here's your problem" but it does give you a place to
start:

- Try going into the DNS console and checking for Resource Records that may
have problems.

- Check that Active Directory is not reporting any errors.

- Try re-loading the zone.

Take a closer look at the event data and see if you can identify the
Resource Record or zone that is causing the problem.

Wish I could be more help.
--
William L. Whipple
EZine.Com

"JL Adamson" <JLAd...@discussions.microsoft.com> wrote in message
news:D4B5BC98-4824-47EB...@microsoft.com...

[JL Adamson]

That's the same thing I get when I search everywhere else. The problem is
that I'm getting a totally different error message. Those articles don't seem
to help.

[P@discussions.microsoft.com Robert P]

Essentialy, the server reporting the error contains the record in it`s local
table. AD reports that the record does not exist, hence the assumption that i
tis corrupt.

If this problem occures after reboot it could be orphaned in AD, because AD
stops earlier than netlogon should de-register records (just thinking loudly).

I`ll try:

Before system reboot manualy stop netlogon, because of his job
(de-registering records).

After reboot, launch the dnsmgmt.msc (dns administartion console), expand
‘reverse lookup zones’, find and select appropriate zone. In the right hand
window, find and delete record(s) referenced in alarm(s).

Wait till replication process complete successful, stop netlogon and reboot
the server. Is there possibility, that another records goes up and would
asking for removal.

Start server and check dns events for errors.

Hope that this would help you

Regards,