Natasha R . Gallaty <[EMAIL PROTECTED]> wrote: > Here is an example: > From Host Report: > 760: 0.59%: 216.239.46.26 (this IP is not found in dnscache.txt, but > name resolves with nslookup)
That can sometimes happen if the server responsible for that IP address is slow. When you did the original lookup, it timed out before the response came back. When you did a subsequent lookup it worked. Normally, that kind of situation is lost in the noise of the 30% or so of hosts that don't resolve at all, and so it's ignored. If you use a 3rd party tool like QDNS, you can strip out addresses that were marked as unresolved, and try again. Addresses that were resolved the first time will still be in the file, and so won't be looked up, but addressed that weren't resolved the first time will be treated as "new", and will be looked up, and some of them may resolve on the second run. (You could probably do the same with Analog by using grep or findstring to discard all the lines with "*" in the DNS cache file). > From dnscache.txt: > 17066694 64.65.238.214 host-64-65-238-214.choiceone.net > > But the same IP from Host Report is not translated > 512: 0.47%: 64.65.238.214 > > If I'm just confused about what the result is supposed to be, please > let me know. No, you're right, I would have expected that one to be used in the Host Report. I don't have any explanation of why it wouldn't be. In fact, when I put that line into a test DNS file, and put the IP number is a test log file, my Host Report does use the name. Aengus +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
