Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The DNS server does not have a cache or other database entry for root name servers. Either the root hints file, cache.dns, or Active Directory must have at least one name server (NS) resource record, indicating a root DNS server and a corresponding host (A) resource record for that root DNS server. Otherwise, the DNS server will be unable to contact the root DNS server on startup and will be unable to answer queries for names outside of its own authoritative zones. To correct this problem, use the DNS console to update the server root hints.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What are the DNS zone files and resource records?
In one case, this event ID appeared on a computer being built as a secondary domain controller on Windows 2003 that was also a DNS server. The DNS "root hints" had all been deleted and a root (.) domain had just been created (because the computer was never going to be connected to the Internet or any other DNS domain).
If DNS "root hints" are required then create them and delete the root domain otherwise ensure that the root domain exists.
See MSW2KDB for information on this event.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated