DNS and Bind Recrusion page 39 (3rd edition)

Joseph S D Yao jsdy at cospo.osis.gov
Thu Sep 2 22:12:47 UTC 1999


> But I still don't see the alleged problem.  Could you be more specific?

I didn't see the initial question, but I think I see what Michael is
talking about.  Third Edition (Sep. 1998), apparently first printing.
P. 30, "Iteration" section.

An iterative query would involve the first-queried name server giving
to the resolver (not "resolve") the name server of the closest match it
knows to the queried name.  This might be a root server.  Said resolver
would then go to that name server, and then iterate until it found the
desired info or a server that said, no more, hold, enough.

If the resolver were doing the iterative resolution.

But application-based resolvers typically only want to do something
simple.  They go to the closest name server, and ask IT to do all the
work for them (recursion).  It is the name server's resolver that does
the iteration described above.  And that is what that third paragraph
in the Iteration section describes, after the "which then" - recursion.

I can see how this might be misconstrued.

--
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
      This message is not an official statement of COSPO policies.


More information about the bind-users mailing list