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.

names within the zone are administered independently of names in other zones.<br />

Authority over zones is vested in the name servers.<br />

Normally, the name servers that have authority for a zone will have domain<br />

names belonging to that zone, but this is not required. Where a domain contains<br />

a subtree that falls in a different zone, the name server or servers with authority<br />

over the superior domain are said to delegate authority to the name server or<br />

servers with authority over the subdomain. Name servers can also delegate<br />

authority to themselves; in this case, the domain name space is still divided into<br />

zones moving down the domain name tree, but authority for two zones is held by<br />

the same server. The division of the domain name space into zones is<br />

accomplished using resource records stored in the Domain Name System.<br />

At the top-level root domain there is an exception to this. There is no higher<br />

system to which authority can be delegated, but it is not desirable to have all<br />

queries for fully qualified domain names to be directed to just one system.<br />

Therefore, authority for the top-level zones is shared among a set of root name<br />

servers 1 coordinated by the ICANN.<br />

To better illustrate the process of resolving a symbolic name to an <strong>IP</strong> address,<br />

consider a query for myHost.myDept.myCorp.com, <strong>and</strong> let us assume that our<br />

name server does not have the answer already in its cache. The query goes to<br />

the .com root name server, which in turn forwards the query to a server with an<br />

NS record for myCorp.com. At this stage, it is likely that a name server has been<br />

reached that has cached the needed answer. However, the query could be<br />

further delegated to a name server for myDept.myCorp.com<br />

As a result of this scheme:<br />

► Rather than having a central server for the database, the work that is involved<br />

in maintaining this database is off-loaded to hosts throughout the name<br />

space.<br />

► Authority for creating <strong>and</strong> changing symbolic host names <strong>and</strong> responsibility<br />

for maintaining a database for them is delegated to the organization owning<br />

the zone (within the name space) containing those host names.<br />

► From the user's st<strong>and</strong>point, there is a single database that deals with these<br />

address resolutions. The user might be aware that the database is<br />

distributed, but generally need not be concerned about this.<br />

1 At the time of writing, there were 13 root servers.<br />

Chapter 12. Directory <strong>and</strong> naming protocols 431

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

Saved successfully!

Ooh no, something went wrong!