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 could not parse the zone file <file> at line <number>. Although the DNS server continues to load, ignoring this line, it is recommended that you either correct the line or remove it from the zone file. The zone file is located in the %SystemRoot%\\System32\\Dns directory.
|English: Request a translation of the event description in plain English.|
This problem occurs if the zone file does not contain WINS Lookup records. The DNS service may start, but the zone is treated as Reverse. As a result, name resolution of hosts contained in the zone do not resolve and it may not be possible to add new records to the zone file using the DNS user interface. This is because the INT zone file was not recognized as Forward when the DNS service was started. See ME239079 to solve this problem.
This problem occurs because there is an invalid HINFO record in the zone file. See ME195669 and "the link to "JSI Tip 0786" for details.
As per Microsoft: "The specified database file might be corrupted due to formatting or syntax errors". See ME203009, ME236460 and MSW2KDB for additional information on this event.
|Private comment: Subscribers only. See example of private comment|
|Links: ME195669, ME203009, ME236460, ME239079, JSI Tip 0876, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated