Getting Data In

WIndows DNS debug log becomes deleted


On a Windows 2008 domain controller, DNS debug logging enabled, so that queries can be captured by Splunk. The DNS debug log is called "D:\dns-log\dns-log.txt"

That file is being monitored by Splunk and it successfully is added to Splunk indexer.

This log file keeps disappearing from its host after some number of hours or days.

If we restart the Microsoft DNS service, the log file is recreated and Splunk resumes indexing, minus the lost period of time when the file was missing.

Is there any way that the Splunk Universal Forwarder could be causing the file to be deleted?

I have not yet enabled Windows file auditing because that is quite resource intensive on the host.

Tags (2)


You should use MonitorNoHande input type instead of monitor since dns log component is very sensitive to file access collisions.

0 Karma


I've already read the "godlessheathenmemoirs" article and the "0x80000000 Logs write-through transactions" setting is enabled in my environment. It hasn't made it any better.

0 Karma

Path Finder

Was you able to find a solution for you problem? I think I may have a similiar issue.

0 Karma

New Member

I came across interesting article when digging for info on the same subject - (not enough karma to paste the link) try googling for "Gathering detailed DNS debug logs from AD DNS" or go to godlessheathenmemoirs blog at blogspot dot com and look at August 2011 archive.

Haven't tried the tricks myself yet (there are always other priorities) but it might help.

0 Karma


Did you ever find the answer to this? It is happening to me too. It seems to be when the log file reached its maximum size it is deleted and recreated and during this process the file creation fails.

Perhaps it fails to recreate the file because Splunk has a file handle on it.

0 Karma


Then this is a non-destructive monitor.

Something else is removing your file.

0 Karma


If your inputs.conf stanza for this input is of the type


Then this is non-destructive. If your inputs.conf stanza for this input is of the type


Then this could be destructive, although such a stanza should also have the line

move_policy = sinkhole

to be properly destructive (e.g., index the file and delete it).


Thanks for the idea -- but we are not using that type of config.

Ours is:

disabled = 0
index = WinEvtDns
sourcetype = dns

0 Karma
Get Updates on the Splunk Community!

What's New in Splunk Cloud Platform 9.2.2403?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.2.2403! Analysts can ...

Stay Connected: Your Guide to July and August Tech Talks, Office Hours, and Webinars!

Dive into our sizzling summer lineup for July and August Community Office Hours and Tech Talks. Scroll down to ...

Edge Processor Scaling, Energy & Manufacturing Use Cases, and More New Articles on ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...