> On Feb 4, 2015, at 11:09 AM, Stephane Bortzmeyer <bortzme...@nic.fr> wrote: > > On Mon, Jan 19, 2015 at 02:16:47PM -0800, > Paul Hoffman <paul.hoff...@vpnc.org> wrote > a message of 17 lines which said: > >> Greetings again. Andrew, Kazunori, and I have done a massive >> revision on the DNS terminology draft based on the input we got on >> the -00. We're sure we have further to go, but we wanted people to >> look over the new version and give feedback. > > I find the definition of Forwarder still confused. I suggest to > rewrite it as: > > DNS forwarder -- When a first resolver receives a DNS query (and > cannot directly answers it), then sends the > query to a second recursive resolver, instead of directly to the > authoritative name servers, this second resolver is called a > forwarder. Section 1 > of RFC 2308 describes a forwarder as "a nameserver used to resolve queries > instead of directly using the authoritative nameserver chain". RFC > further says "The forwarder typically either has better access to > the internet, or maintains a bigger cache which may be shared amongst > many resolvers.” >
I do not think this helps. Forwarding is not always a capacity/access issue but policy decision to improve site resolution cache hit ratio among a farm of resolvers. Forwarding resolver by policy does not do recursion but requests upstream to perform recursion. Olafur _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
