Version 0.0.1.6 (ALPHA) - for Windows98 or NT
Copyright(c) 2000, Keith Schmit (MAD Programming)
W3CDNS is a quick app I cranked out to process Microsoft W3C Extended IIS site logs. The application is a bare-bones command-line type app, which processes an input file and dumps a new file with resolved IP addresses.
I know there's tools on the market to process various types of logs, but none of them did a direct W3C IP only->W3C resolved log conversion.
Thanks go out to the WinShoes (now Indy) team for the DNS components used in this application.
Please note: I have tested this, but I would NEVER use it against archival copies of your IIS logs-make a separate copy into a new directory and process from those. I have only tested against IIS 4.0, but I'm reasonably sure it will work against IIS 3 W3C logs.
The command line parameters for this app are as follows:
W3CDNS <input> <output> <cachesize> <timeout> [/help | /nocache | /silent]
- <input> The file to process (wildcards are acceptable)
- <output> The output file or directory to write the processed logs to. If a directory is supplied the original filename is used when writing the output files. Please DO NOT use the same path as the original file! The app will happily squish your log files and crash.
- <cachesize> # of cache lines to maintain for DNS. I recommend at least 2000. Max 5000.
- <timeout> DNS timeout value. I recommend a setting of 10, lower than 5 is too short.
Please note the above parameters must all be supplied since the parameters are parsed in the order documented. The optional switches MUST be at the end.
- /help - Dumps a help dialog and exits
- /nocache - Program will not load or save the ip.cache file from the program directory
- /silent - Silent operation (no dialog) I have not tested this option.
Please note that the program will always use an internal cache during DNS processing. If you supply a number for cache < 1000 you cause an EXTREME slowdown of DNS processing, on the order of 2x-10x depending on how low you set the cache size.
The program will by default look for a DNS cache written to ip.cache in the same directory as the application. If this exists and the /nocache switch is not supplied, the app will load it's initial cache from the file, and at the end of file processing will write it's final DNS cache to the same file.
If you have any suggestions for improvement, or bug reports, please send me an email at firstname.lastname@example.org, and I will do my best to get back to you. I do intend to make some improvements to this application in the future, but it's done what I needed it to do, and I'm not able to support this on a regular basis. I do have one of those day job thingies after all. Source code is not available. Please do not ask for it.
COPYRIGHT (C) 2000, KEITH SCHMIT. I RESERVE ALL RIGHTS TO THIS APPLICATION (W3CDNS). YOU MAY USE THIS APPLICATION WITHOUT CHARGE, BUT MAY NOT DISTRIBUTE IT BY ANY MEANS OR IN ANY FORM WITHOUT MY PREVIOUS WRITTEN CONSENT DELIVERED BY US POSTAL MAIL. YOU MAY LINK TO THIS COMPRESSED ARCHIVE ON MY WEBSITE AT ANY TIME.
I HAVE TESTED THIS APPLICATION, BUT DO NOT GUARENTEE IT AGAINST ANY DAMAGE CAUSE DURING IT'S USE, INTENTIONAL OR UNINTENTIONAL. ALL RISK IS TAKEN BY THE USER OF THIS APPLICATION.
USE OF THE W3C APPLICATION CONSTRUES ACCEPTANCE OF THIS AGREEMENT.