25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

12.1 Domain Name System (DNS)<br />

The Domain Name System is a st<strong>and</strong>ard protocol with STD number 13, <strong>and</strong> its<br />

status is recommended. It is described in RFC 1034 <strong>and</strong> RFC 1035. This section<br />

explains the implementation of the Domain Name System <strong>and</strong> the<br />

implementation of name servers.<br />

The early Internet configurations required the use of only numeric <strong>IP</strong> addresses.<br />

Because this was burdensome <strong>and</strong> much harder to remember than just the name<br />

of a system, this evolved into the use of symbolic host names. For example,<br />

instead of typing:<br />

TELNET 10.12.7.14<br />

You can type:<br />

TELNET MyHost<br />

MyHost is then translated in some way to the <strong>IP</strong> address 10.12.7.14. Though<br />

using host names makes the process of accessing a resource easier, it also<br />

introduces the problem of maintaining the mappings between <strong>IP</strong> addresses <strong>and</strong><br />

high-level machine names in a coordinated <strong>and</strong> centralized way.<br />

Initially, host names to address mappings were maintained by the Network<br />

Information Center (NIC) in a single file (HOSTS.TXT), which was fetched by all<br />

hosts using FTP. This is called a flat namespace. But due to the explosive growth<br />

in the number of hosts, this mechanism became too cumbersome (consider the<br />

work involved in the addition of just one host to the Internet) <strong>and</strong> was replaced by<br />

a new concept: Domain Name System. Hosts on smaller networks can continue<br />

to use a local flat namespace (the HOSTS.LOCAL file) instead of or in addition to<br />

the Domain Name System. Outside of small networks, however, the Domain<br />

Name System is essential. This system allows a program running on a host to<br />

perform the mapping of a high-level symbolic name to an <strong>IP</strong> address for any<br />

other host without requiring every host to have a complete database of host<br />

names.<br />

12.1.1 The hierarchical namespace<br />

Consider the typical internal structure of a large organization. Because the chief<br />

executive cannot do everything, the organization will probably be partitioned into<br />

divisions, each of them having autonomy within certain limits. Specifically, the<br />

executive in charge of a division has authority to make direct decisions, without<br />

permission from the chief executive.<br />

426 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!