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.

When a domain is registered with the root <strong>and</strong> a separate zone of authority<br />

established, the following rules apply:<br />

► The domain must be registered with the root administrator.<br />

► There must be an identified administrator for the domain.<br />

► There must be at least two name servers with authority for the zone that are<br />

accessible from outside <strong>and</strong> inside the domain to ensure no single point of<br />

failure.<br />

We also recommend that name servers that delegate authority apply these rules,<br />

because the delegating name servers are responsible for the behavior of name<br />

servers under their authority.<br />

12.1.9 Domain Name System resource records<br />

The Domain Name System's distributed database is composed of resource<br />

records (RRs), which are divided into classes for different kinds of networks. We<br />

only discuss the Internet class of records. Resource records provide a mapping<br />

between domain names <strong>and</strong> network objects. The most common network objects<br />

are the addresses of Internet hosts, but the Domain Name System is designed to<br />

accommodate a wide range of different objects.<br />

A zone consists of a group of resource records, beginning with a Start of<br />

Authority (SOA) record. The SOA record identifies the domain name of the zone.<br />

There will be a name server (NS) record for the primary name server for this<br />

zone. There might also be NS records for the secondary name servers. The NS<br />

records are used to identify which of the name servers are authoritative (see<br />

“Domain name resolver operation” on page 434). Following these records are the<br />

resource records, which might map names to <strong>IP</strong> addresses or aliases to names.<br />

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