Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
Name Resolution Techniques and Functional Elements of A Name Resolution System
(Page 2 of 2)
Client/Server Resolution Functional Elements
The last of these three methods is
the one used for most large, modern name systems. The client/server
method of request/reply resolution is similar to how many other protocols
function. One thing that is unique about name resolution, however, is
that name resolution isn't often invoked directly by the client. It's
rare, for example, for a human user to say please resolve the
following name. We also certainly wouldn't want a user to have
to manually resolve a name to an address each time they wished to contact
a device, as this would be cumbersome.
Instead, the system is automated
by having software accept machine names input by users. The software
resolves the name by passing it to a name resolver software component.
The resolver acts as the client in the name resolution process. It contacts
a name server, which responds to the request. The name resolver
and name server constitute the two main functional elements in name
In a distributed database for a hierarchical
name system, multiple requests may be required, since name servers will
contain only information for certain machines and not others. Resolvers
follow a special procedure to travel the hierarchy until
they find the server that has the information they want. Again, TCP/IP's
Domain Name System (DNS) name resolution
is the best example of this method.
Key Concept: Name resolution is arguably the most important of the main functional elements of a name system, because it is the part of the system that actually converts names into addresses. The two main components of name resolution are name resolvers, which act as clients in the resolution process, and name servers. The three main name resolution methodstable-based, broadcast and client/servercorrespond closely to the table, broadcast and database methods of name registration.
|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!|
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.