<Tr> <Td> later boot sequence </Td> <Td>! Boot. Choices. Hardware. Disabled. Internet. Files. Hosts </Td> </Tr> <P> The ARPANET, the predecessor of the Internet, had no distributed host name database . Each network node maintained its own map of the network nodes as needed and assigned them names that were memorable to the users of the system . There was no method for ensuring that all references to a given node in a network were using the same name, nor was there a way to read the hosts file of another computer to automatically obtain a copy . </P> <P> The small size of the ARPANET kept the administrative overhead small to maintain an accurate hosts file . Network nodes typically had one address and could have many names . As local area TCP / IP computer networks gained popularity, however, the maintenance of hosts files became a larger burden on system administrators as networks and network nodes were being added to the system with increasing frequency . </P> <P> Standardization efforts, such as the format specification of the file HOSTS. TXT in RFC 952, and distribution protocols, e.g., the hostname server described in RFC 953, helped with these problems, but the centralized and monolithic nature of hosts files eventually necessitated the creation of the distributed Domain Name System (DNS). </P>

Hosts file used by microsoft tcp/ip for windows