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.

The following figure shows the general format of a resource record (Figure 12-4).<br />

Figure 12-4 DNS general resource record format<br />

Where:<br />

Name The domain name to be defined. The Domain Name System is<br />

very general in its rules for the composition of domain names.<br />

However, it recommends a syntax for domain names that<br />

minimizes the likelihood of applications that use a DNS<br />

resolver (that is, nearly all <strong>TCP</strong>/<strong>IP</strong> applications) from<br />

misinterpreting a domain name. A domain name adhering to<br />

this recommended syntax will consist of a series of labels<br />

consisting of alphanumeric characters or hyphens, each label<br />

having a length of between 1 <strong>and</strong> 63 characters, starting with<br />

an alphabetic character. Each pair of labels is separated by a<br />

dot (period) in human-readable form, but not in the form used<br />

within DNS messages. Domain names are not case-sensitive.<br />

Type Identifies the type of the resource in this record. There are<br />

numerous possible values, but some of the more common<br />

ones, along with the RFCs which define them, are listed in<br />

Table 12-2 on page 438.<br />

Class Identifies the protocol family. The only commonly used value is<br />

IN (the Internet system), though other values are defined by<br />

RFC 1035 <strong>and</strong> include:<br />

CS (value 2): The CSNET class. This has been obsoleted.<br />

CH (value 3): The CHAOS class.<br />

HS (value 4): The Hesiod class.<br />

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

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

Saved successfully!

Ooh no, something went wrong!