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.

The Book is Here... and Now On Sale!

Searchable, convenient, complete TCP/IP information.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  Name Systems and TCP/IP Name Registration and Name Resolution
           9  TCP/IP Name Systems: Host Tables and Domain Name System (DNS)

Previous Topic/Section
TCP/IP Name Systems: Host Tables and Domain Name System (DNS)
Previous Page
Pages in Current Topic/Section
1
2
Next Page
TCP/IP Host Table Name System
Next Topic/Section

Overview and History of TCP/IP Host Names and Name Systems
(Page 1 of 2)

In the section that introduces name systems and describes the concepts behind them, I described an interesting paradox. Even though name systems aren't strictly necessary for the functioning of a networking system, they make using a network so much easier for people that they are considered an essential part of most networks. I think no better evidence of this can be found than the history of name system development in TCP/IP.

Early Use of Host Names on the ARPAnet

In fact, the history of name systems in the TCP/IP protocol suite actually goes back well before TCP and IP were themselves even created! In the late 1960s and early 1970s, when the predecessor of the Internet (the ARPAnet) was being developed, it used older networking protocols that served the same function that TCP and IP do today. The ARPAnet was very small by today's standard, containing at first only a few machines, called hosts just as TCP/IP machines often are today. The addressing scheme was also very simple: just the combination of an IMP (computer) number and a port number for each host.

With only a handful of machines names it was easy to memorize addresses, but as the ARPAnet grew to several dozen machines this became untenable. As early as 1971, it was apparent to the engineers designing the ARPAnet that symbolic names were much easier for everyone to work with than numeric addresses. They began to assign simple host names to each of the devices on the network. Each site managed its own host table that listed the mappings of names to addresses.

The First ARPAnet Name System: Host Name Lists

Naturally, the ARPAnet engineers immediately recognized the dangers of having each site maintain a list of possibly inconsistent host names. Since the internetwork was just a small “club” at this point, they used the RFC process itself to document standard host name to address mappings. RFC 226, Standardization Of Host Mnemonics, is the first RFC I could find showing how host names were assigned. It was published on September 20, 1971.

This initial name system was about as manual as a system could be. As additions and changes were made to the network, the list of host names was updated in a new RFC, leading to a series of RFCs being published in the 1970s. Each host administrator still maintained his or her own host table, which was updated when a new RFC was published. During this time, the structure of host names was still under discussion and changes were made to just about every aspect of the name system as new ideas were explored and refined.

This worked fine while the ARPAnet was very small, but had many problems. One was that it was extremely slow in responding to network modifications; additions or changes would only be entered into device tables after a new list was published. Even with the centralized list, there were also still potential consistency issues, if a site manager forgot to update a file or made a typographical error. These were in addition to the usual limitations of a host-table-based name system.


Previous Topic/Section
TCP/IP Name Systems: Host Tables and Domain Name System (DNS)
Previous Page
Pages in Current Topic/Section
1
2
Next Page
TCP/IP Host Table Name System
Next Topic/Section

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!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



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.