Re: Two new DNS virtual packages (authoritative-name-server & recursive-name-server)
On Tue, 22 Oct 2013, Russ Allbery wrote:
> > I would suggest: caching-name-server
> That's basically what a recursive-name-server is. I don't think the
> application should care whether it caches locally or not; that's up to the
> local administrator.
Almost every recursive resolver does caching, to the point that anything
that needs a remote caching namerserver can expect it to just exist.
Usually, the worst you can expect is two levels: local-system -> crap SOHO
device DNS proxy -> DNS recursive server with caching.
When something actually bothers to specify that it wants a caching
name-server, it means a close-by (latency-wise) caching name-server, or an
exclusive caching nameserver.
Heck, mail clusters often need an hierarchy of a local high-performance
caching resolver per node AND a cluster-wide pair of full-blown
high-performance caching recursive resolvers and private authoritative
resolvers (for the RBL feeds).
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot