| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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 resolution. 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.
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||