Re: [Summary-Talk] Caching bad DNS stuff

[Jason Linhart <jason@xxxxxxxxxxx>]

On 9/9/03 2:46 PM a.h.s. boy (spudlists@nothingness.org) wrote:

>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.
>
>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?

Summary is just calling the standard system call to lookup a domain name, 
it doesn't do any caching of the results it's self. It is probably the 
local DNS server that is doing the caching of the lookup. Caching results 
for some time is standard practice for DNS servers. "nslookup" and "dig" 
do their own resolutions, they might well not use the same DNS servers as 
the standard system calls, so that isn't really diagnostic. If you reset 
the local DNS server that would probably solve it.

The most reliable work around would be to configure Summary with a 
download URL that specifies an IP address instead of a domain name. That 
will never have lookup problems.

Jason

-----------------
Jason@Summary.Net
-----------------
Dr. Seuss books . . . can be read and enjoyed on several levels. For
example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed
as a searing indictment of the narrow-minded binary counting system.
  -- Peter van der Linden, Expert C Programming, Deep C Secrets
-------------
Go to <http://summary.net/list.html> to update subscription info.