1

Cache of BIND is kinda of a "Black hole" for me. I know about TTL and that it can be overridden. I know that there's a way to dump cache into a file that could be viewed in a text editor. But, still, lots of things are in the dark. I've read that once you reboot, the cache is lost. Then why to build the cache from scratch each time you turn on your computer? What, like BIND's building its cache for a few hours when the server is on and then simply loose it? That doesn't make sense. Why it can't be kept in a file or in a database? Is it a limitation or something good? Unfortunately, I didn't find in books or on the Internet clear information about all of this. So please explain it to me in simple English OR just provide the links to the relevant source of information.

2
  • 1
    For starters, most Bind installations run continuously.
    – Halfgaar
    Nov 8, 2015 at 12:48
  • 1
    DNS cache entries have very short lifetimes to begin with, and re-fetching expired (or absent) entries is an incredibly low-load process. Having to re-build a few hundred KB of cache is not a big deal. Besides, like @Halfgaar said, your DNS service should be on a server that is always running alyway b
    – EEAA
    Nov 8, 2015 at 13:11

1 Answer 1

0

BIND's cache is an in memory structure. On large recursive servers it could potentially be many GB in size.

It would make BIND much slower if it had to persist that structure to disk, for negligible gain.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .