Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 3152 Source: DNS

The DNS server was unable to open file dns\dns.log for write. Most likely the file is a zone file that is already open. Close the zone file and re-initiate zone write. Data: 0000: 20 00 00 00
As per Microsoft: "You might not have permission to access this file". See MSW2KDB for additional information about this event.
The file dns.log, usually located at systemroot\System32\Dns\Dns.log is a DNS debug file. Probably, the DNS server can not write to that file as it is opened by another process (ex: a text editor).
This may be caused by file system corruption, backup in progress, anti-virus activity or any other situation when the DNS Server cannot access the log file.
This event can occur if you use the DNS administrative MMC console very fast. You may try to write to the zonefile while it is being read by your own console. Close the MMC console and open it again.
In my case, I got this error message when the DNS server did not had the time to create the proper _udp records. So I stoped the DNS service. 1 or 2 minutes after the DNS start the _udp records were created and the 3152 disappeared.

Windows Event Log Analysis Splunk App

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



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.