Re: [Summary-Talk] Corrupt DNS cache file?

[Jason Linhart <jason@xxxxxxxxxxx>]

Once you get bad entries in the DNS cache they will stay there for at
least 18 weeks, and often longer, unless you do something. There are two
steps, fixing the DNS cache file, and if you are using incremental mode
you also need to fix the current incremental database.

The simplest way to fix the dnscache file is to delete it. The dnscache
file is located in Summary's Data folder. This will force Summary to do
all of the lookups over again, which may take quite a while.

If you are feeling more adventurous you can go into the dnscache file
with a text editor and manually delete all of the failed entries. You
want to delete all of the lines that end with a "*". They will look
something like:

18816299 211.221.239.227 *

If you are running in incremental mode you will probably also want to
restore a backup from before the bad DNS lookups. That will clear the
bad lookup results from the incremental database. You will need to have
the log files back to at least that point. You can restore a backup on
the Tools configuration page. Look for the most recent one from before
the failed lookups.

Good Luck
Jason


Luc Dubois wrote:
> 
> I've somehow managed to mess up the DNS cache file (I think).
> 
> So, I think I have 2 problems: 1) bring the cache back in a state
> that allows proper processing of IPs the next time I run Summary, and
> 2) retrieve the domain names for all IPs that are still numeric only.

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