|
DNS Basic Name Resolution Techniques: Iterative and Recursive Resolution
(Page 3 of 4)
Recursive Resolution
When a client sends a recursive request
to a name server, the server responds back with the answer if it has
the information sought. If it doesn't, the server takes responsibility
for finding the answer by becoming a client on behalf of the original
client and sending new requests to other servers. The original client
only sends one request, and eventually gets the information it wants
(or an error message if it is not available). This technique is shown
in Figure 244.
Figure 244: Recursive DNS Name Resolution This is the same theoretical DNS resolution that I showed in Figure 243, but this time, the client asks for the name servers to perform recursive resolution and they agree to do so. As in the iterative case, the client sends its initial request to the root name server. That server doesnt have the address of C.B.A., but instead of merely returning to the client the address of the name server for A., it sends a request to that server itself. That name server sends a request to the server for B.A., which in turn sends a request to the server for C.B.A.. The address of C.B.A. is then carried back up the chain of requests, from the server of C.B.A. to that of B.A., then A., then the root, and then finally, back to the client.

|
| If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |
|
|
Home -
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.
|