Using named_dump.db to preserve cache across reboots

[phn at icke-reklam.ipsec.nu]

Mr Toad <rat_love_cat at yahoo.co.uk> wrote:

> On 11 Mar 2002 09:16:28 -0800, Jim Reid <jim at rfc1035.com> wrote:
>>Why? What's the point of preserving a cache that is by definition now
>>out of date? Would you expect the weather forecast to tell you what
>>the weather was like 2 weeks ago? And if it did, what use would that
>>be to anyone?

> The reason for wanting to preserve the cache is because, over time, my
> nameserver builds up a rich cache which speeds up lookups for
> commonly-requested names.  Now if I reboot the machine, that cache is
> lost and will take time to grow back.  I would prefer to be able to
> preserve the cache across reboots so that it is not lost.

> I can't understand why you say that it's like asking for last week's
> weather forecast.  Surely the nameserver cache is just as valid after
> a reboot as it was a couple of minutes before?

Sound to me that avoiding reboots would cure the problems.

> Mr Toad



-- 
Peter Håkanson         
        IPSec  Sverige      (At the Riverside of Gothenburg, home of Volvo)
           Sorry about my e-mail address, but i'm trying to keep spam out.
	   Remove "icke-reklam" and it works.