On Fri, 23 Sep 2016, RW wrote:
On Thu, 22 Sep 2016 20:24:21 -0700 (PDT)
John Hardin wrote:
Lists shouldn't have said "caching", that confuses the issue. Caching
and recursion are two different, unrelated pieces.
Focus on the "recursion" and "no forwarding" parts of that
recommendation.
I've been wondering whether recursive is actually the correct term.
As I understand it there are two types of DNS lookup:
1. Iterative - where results are found by working down through
multiple servers from the root servers.
"Recursive" is the way I have always heard that described.
2. Recursive - where a request is made to a single nameserver which
handles the whole look-up on behalf of a client.
"Forwarding" is the way I have always heard that described.
What this turns on is whether a forwarding server is a distinct
class of of nameserver or a type of recursive server. I think the
latter is most logical, since both provide a recursive interface.
Definitions of the term "recursive server" that I've seen contrast it
only with "authoritative server".
One thing is certain, what you want is a name server that does
*iterative* lookups.
I think the clearest way to state it is "must not forward" as
lists did.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
One death is a tragedy; thirty is a media sensation;
a million is a statistic. -- Joseph Stalin, modernized
-----------------------------------------------------------------------
276 days since the first successful real return to launch site (SpaceX)
