RR
Click on the red underlined text to get to the source
...
This document defines the format of one new Resource Record (RR) for
the DNS for domain name ...
...
NSAP-to-name translation is accomplished through use of the PTR RR
(see RFC 1035std13 for a description of the PTR RR ...
... RR
(see RFC 1035std13 for a description of the PTR RR). This paper describes
how PTR RRs are used to support this translation.
...
... 1035std13 for a description of the PTR RR). This paper describes
how PTR RRs are used to support this translation.
This memo assumes that the reader is familiar with the DNS ...
...
In the NSAP RRs in Master Files and in the printed text in this memo,
NSAPs are often represented as a string of "."-separated hex values.
...
... NSAP RRs conform to the top level RR format and semantics as defined
in Section 3.2.1 of RFC 1035std13 ...
... resource record may be cached before the source
of the information should again be consulted. Zero values are
interpreted to mean that the RR can only be used for the
transaction in progress, and should not be cached. For example,
...
... The PTR RR is defined in RFC 1035std13. This RR is typically used under
the "IN-ADDR.ARPA" domain ...
... according to the rules described below. A query is sent by the
resolver requesting a PTR RR for the provided domain name.
...
... NSAP RRs (and NSAP-related PTR RRs) in Master Files
conforms to Section 5, "Master Files," of RFC 1035std13. Below are
...
... conforms to Section 5, "Master Files," of RFC 1035std13. Below are
examples of the use of these RRs in Master Files to support name-to-
NSAP and NSAP ...
...
The NSAP RR introduces a new hex string format for the RDATA field.
The format is "0x" (i.e., a zero followed by an 'x' character)
...