[getdns-api] Priming the cache

William Chan (陈智昌) willchan at chromium.org
Wed Mar 13 08:07:48 MST 2013

I think the feature is reasonable, but I don't understand why it should be
part of the API. Can someone explain why this is the best place to put it?
Why not keep this implementation specific?

The reason I ask is, does this require all implementations of this API to
implement a cache? That seems like unnecessary burden on implementations,
since I can imagine many implementations simply proxying DNS queries to
some other service that may implement caching.

On Wed, Mar 13, 2013 at 10:56 AM, Paul Hoffman <paul.hoffman at vpnc.org>wrote:

> On Mar 12, 2013, at 5:39 PM, Murray S. Kucherawy <superuser at gmail.com>
> wrote:
> > This one's a bit of a long shot request, but I really wish the existing
> interfaces could do this so I'll ask for it here.
> >
> > A lot of my recent open source projects (e.g., DKIM and its pals) rely
> on getting policy and key information from the DNS.  Being able to run
> tests on the DNS handling code is an important part of comprehensive unit
> testing prior to a release.  Sometimes it's necessary to run such tests on
> a machine without Internet access.  Thus, being able to force data into the
> resolver that later queries will retrieve is an exceedingly useful notion.
>  If the resolver has a cache, this is just the ability to go about having a
> test harness prime the cache before issuing queries.
> This seems like a reasonable advanced feature.
> --Paul Hoffman
> _______________________________________________
> getdns-api mailing list
> getdns-api at vpnc.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vpnc.org/pipermail/getdns-api/attachments/20130313/7d4c3153/attachment.html>

More information about the getdns-api mailing list