Update: the log file monitor is not appropriate as workaround, but File & Directory Change monitor is, unchecking file date and checking MD5 hash value to detect any change and using script: del domainrecords.txt nslookup -querytype=mx mydomain.com >> domainrecords.txt nslookup -querytype=txt mydomain.com >> domainrecords.txt nslookup -querytype=cname mydomain.com >> domainrecords.txt

Update: the log file monitor is not appropriate as workaround, but File & Directory Change monitor is, unchecking file date and checking MD5 hash value to detect any change and using script: del mxrecords.txt domainrecords.txt nslookup -querytype=mx mydomain.com >> mxrecords.txtdomainrecords.txt nslookup -querytype=txt mydomain.com >> domainrecords.txt nslookup -querytype=cname mydomain.com >> domainrecords.txt

Update: the log file monitor is not appropriate as workaround, but File & Directory Change monitor is, unchecking file date and checking MD5 hash value to detect any change and using script: del c:\some_directory\mxrecords.txt mxrecords.txt nslookup -querytype=mx mydomain.com >> c:\some_directory\mxrecords.txtmxrecords.txt

Update: the log file monitor is not appropriate as workaround, but File & Directory Change monitor is, unchecking file date and checking MD5 hash value to detect any change and using script: del c:\some_directory\mxrecords.txt nslookup -querytype=mx mydomain.com >> c:\some_directory\mxrecords.txt

Update: the log file monitor is not appropriate as workaround, but File & Directory Change monitor is, unchecking file date and checking MD5 hash value to detect any change and using script: del c:\some_directory\mxrecords.txt nslookup -querytype=mx mydomain.com >> c:\some_directory\mxrecords.txt