[Summary-Talk] Caching bad DNS stuff

["a.h.s. boy" <spudlists@xxxxxxxxxxxxxxx>]

I have a recurring problem with Summary failing to download log files 
from a remote server. The log spits out "Host not found", and Summary 
continues on to (re)process the old log files. Consequently, I get new 
reports based on old log files.

The problem seems to occur after there's been a DNS problem of some 
sort, I assume when Summary has tried to run, e.g. the DNS server goes 
down, Summary attempts a processing run, and fails to locate the hosts 
properly. That much I don't really have a problem with, since Summary 
legitimately couldn't find the host, though I do wonder why it doesn't 
seem to be using the secondary DNS configured on the machine.

However, even after DNS service has been restored, Summary appears to 
have cached the "Host not found" entries, so future processing runs all 
seem to fail without trying particularly hard to lookup the addresses 
again. I have to quit Summary and restart it in order for it to locate 
the hostnames properly.

Is this a bug? While a simple nslookup or dig works fine, Summary still 
says "Host not found". Is there a cache file I can have a cronjob 
delete periodically that only applies to log downloading lookups? Is 
there some workaround?

Cheers,
spud.

-------------------------------------------------------------------
a.h.s. boy
spud(at)nothingness.org            "as yes is to if,love is to yes"
http://www.nothingness.org/
-------------------------------------------------------------------
-------------
Go to <http://summary.net/list.html> to update subscription info.