says that this can happen when that particular DC/DNS server has lost its Secure channel with itself or PDC. The article provides some suggestions on how to fix this.
From a newsgroup post:
This event usually occurs because the AD isn't quite ready when the DNS server service starts. It's normally not something you need to worry about provided the event only occurs at boot time. You can also test this by moving the zone(s) to standard primary non active directory integrated and see if they occur ... chances are that they won't."
From a newsgroup post: "I've seen this several times on Win2k3, seems like a bug to me, when you remove AD (and the DNS data in it), it leaves the registry keys behind. Since AD no longer exists on the server, it cannot load the zones.
Go here and delete the keys for the zones noted in the Event.
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server\Zones"
In my case, the "dnscmd /EnumDirectoryPartitions" command did not show that partition. It was something left there after a domain rename. The solution was to clean it from the registry: HKLM\Software\Microsoft\Windows NT\Current Version\DNSserver\.
This event can be ignored if it occurred when Windows was started in Active Directory Restore mode or some other form of Safe Mode. Otherwise, investigate further.
for details on this event.