[bind10-dev] Proposal for a BIND 10 shared cache resolver

[JINMEI Tatuya / 神明達哉]

At Fri, 22 Feb 2013 10:14:44 +0100,
Carsten Strotmann <carsten at strotmann.de> wrote:

> >> the attached idea on how a BIND 10 resolver with a shared cache
> >> could be implemented came to my mind today. Please excuse me if
> >> this has already been discussed somewhere, or if it is total
> >> bogus.
> >> 
> >> The idea stretches the DNS protocol quite a bit, but at least for
> >> me it has some charm.
> > 
> > I admit it looks elegant in a way. But I'm afraid this will have
> > quite poor performance.
> 
> Yes, it is quite a crazy idea.

My quick initial impression was the same (not the crazy part but the
performance concern): handling raw DNS messages is relatively
expensive, so I suspect it's better to avoid having that overhead in
performance sensitive operations such as cache lookup or update.

But it looks like an interesting idea to provide cache management
interface over DNS so even a remote user can manage the cache content
using dig or nsupdate (+ maybe TSIG).  I guess it can better be
implemented as a separate UI module.  This module itself doesn't have
to be fast, so probably written in Python using BIND 10 Python API,
and accepts DNS queries/updates and converts them to native cache
management API/internal-RPC.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.