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.6 Mapping <strong>IP</strong> addresses to domain names: Pointer queries<br />

The Domain Name System provides for a mapping of symbolic names to <strong>IP</strong><br />

addresses <strong>and</strong> vice versa. While the hierarchical structure makes it easy in<br />

principle to search the database for an <strong>IP</strong> address using its symbolic name, the<br />

process of mapping an <strong>IP</strong> address to a symbolic name cannot use the same<br />

process. Therefore, there is another namespace that facilitates the reverse<br />

mapping of <strong>IP</strong> address to symbolic name. It is found in the domain in-addr.arpa<br />

(arpa is used because the Internet was originally the ARPAnet).<br />

Not including <strong>IP</strong>v6, <strong>IP</strong> addresses are normally written in dotted decimal format,<br />

<strong>and</strong> there is one layer of domain for each hierarchy. Contrary to domain names,<br />

which have the least-significant parts of the name first, the dotted decimal format<br />

has the most significant bytes first. Therefore, in the Domain Name System, the<br />

dotted decimal address is shown in reverse order.<br />

For example, consider the following <strong>IP</strong>v4 address:<br />

129.34.139.30<br />

The in-add.arpa address for this is:<br />

30.139.34.129.in-addr.arpa.<br />

This is h<strong>and</strong>led slightly different for <strong>IP</strong>v6 addresses. Because of the <strong>IP</strong>v6<br />

address’ structure, the reverse order is done in nibbles in stead of octets. Also,<br />

the in-addr.arpa domain does not include <strong>IP</strong>v6. Instead, the domain used is<br />

<strong>IP</strong>6.ARPA. For example, consider the following <strong>IP</strong>v6 address:<br />

4321:0:1:2:3:4:567:89ab<br />

Breaking this into nibbles, reversing the odder, <strong>and</strong> appending the domain yields:<br />

b.a.9.8.7.6.5.0.4.0.0.0.3.0.0.0.2.0.0.0.1.0.0.0.0.0.0.0.1.2.3.4.<strong>IP</strong>6.ARPA<br />

Given an <strong>IP</strong> address, the Domain Name System can be used to find the<br />

matching host name. A domain name query to do this is called a pointer query.<br />

12.1.7 The distributed name space<br />

The Domain Name System uses the concept of a distributed name space.<br />

Symbolic names are grouped into zones of authority, more commonly referred to<br />

as zones. In each of these zones, one or more hosts has the task of maintaining<br />

a database of symbolic names <strong>and</strong> <strong>IP</strong> addresses within that zone, <strong>and</strong> provides a<br />

server function for clients who want to translate between symbolic names <strong>and</strong> <strong>IP</strong><br />

addresses. These local name servers are then (through the internetwork on<br />

which they are connected) logically interconnected into a hierarchical tree of<br />

domains. Each zone contains a part or a subtree of the hierarchical tree, <strong>and</strong> the<br />

430 <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!