Using named_dump.db to preserve cache across reboots

Barry Margolin barmar at genuity.net
Fri Mar 8 16:59:28 UTC 2002


In article <a6ap65$bck at pub3.rc.vix.com>,
Mr Toad  <rat_love_cat at yahoo.co.uk> wrote:
>
>I'm running BIND 8.2.3 on Debian Linux 2.2 and would like to be able
>to preserve the cached RRs across reboots.
>
>I know that sending SIGINT to the named process causes bind to dump
>its database to "named_dump.db", and I wonder if this can be used to
>preserve the cached records so they could be reloaded after a reboot.
>
>Is this a supported or reasonable thing to do, or is the named_dump.db
>dumpfile not suitable for this?

It's not suitable.  BIND has no built-in provision for preserving the
cache.  named_dump.db is for diagnosing problems (e.g. finding out who
poisoned your cache).

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list