This error is common at startup if you have only one DC with DNS in a
domain. It is caused from a catch-22 situation, AD cannot start without DNS,
when DNS starts since AD has not started, DNS cannot load the zone.
IF you add a DC, then point the DCs to one other DC and itself for DNS,
should stop this. If you only have one DC use standard primary zones or
ignore the error. Preferably ignore the error because there is no security
on standard primary zones.
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
Keep a back up of your OE settings and folders