>>>>> "Peter" == Peter Koch <[EMAIL PROTECTED]> writes:
Peter> "recursive service" exists, but that's what offered by
Peter> "recursive resolvers". While "recursive name server" is
Peter> unambiguous in this context, I consider this term
Peter> technically incorrect. We're clearly after resolvers, not
Peter> servers here. One might although argue, that *recursive*
Peter> resolver is overspecified because at least I can't imagine
Peter> a non-recursive resolver.
Peter> Coming from the educational perspective and remembering
Peter> lots of operational hassle due to misidentification of
Peter> servers vs. resolvers I'm clearly in favor of the term
Peter> resolver here.
Hmmm. Just saying "resolver" could be confusing. This is generally
used (and understood to denote) a stub resolver: something that is
usually non-recursive. How about using "full service resolver" to
indicate something, usually a name server, that gets queried by stub
resolvers and makes iterative lookups to resolve those queries? This
is the term used by the DNSSEC people for the thing that resolves
queries and validates signatures, caches answers, keeps track of RTTs
and so on.
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
