TCP/IP Host Table Name System
(Page 2 of 4)
Host Table Name Resolution
Name resolution in this system is very simple. Each device reads the host table into memory when it starts up. Users of the system can make reference to the names in that host table in their invocation of various applications, by using a name instead of a numeric IP address. When the software detects a name has been used in this manner, it refers the name to the internal resolver routine in the device, which looks up the name in the host table in memory and returns its address. There is no need for any transmissions or servers to be contacted; resolution is entirely local.
Now, here is the part where I am supposed to say that name registration in the host table name system is simple as well, right? Well, yes and no. From a purely technical standpoint it certainly is: a name is registered on a particular device when the name and corresponding IP address is entered into the device's host table, and that's it.
However, name registration is much more complicated from an administrative standpoint, and this is in fact where we find the major weakness of using host tables. Each network device maintains its own host table independent of the others, usually stored as a file on its local hard disk. This is in contrast to database registration systems where the data is centrally stored and managed. This leads to two very important concerns:
The original mechanism for this was simply hand-editing, with administrators consulting updated published lists of device names. This was a very inefficient method that was prone to error and slow to acknowledge changes to the network. The revised system used a centrally-managed master file that was downloaded by all sites on a regular basis. Name registration in this method required that the name/address mapping be submitted to the authority managing the central file, the Network Information Center (NIC).
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.