RDATA
Click on the red underlined text to get to the source
... An "RR of unknown type" is an RR whose RDATA format is not known to
the DNS implementation at hand, and whose type is not an assigned
...
... class specific, an RR is
considered to be of unknown type when the RDATA format for that
combination of type and class is not known.
...
... servers and resolvers MUST handle RRs of unknown type transparently.
That is, they must treat the RDATA section of such RRs as
unstructured binary data ...
... RR type is known
to some but not all of the servers involved, servers MUST also
exactly preserve the RDATA of RRs of known type, except for changes
due to compression ...
... RRs containing compression pointers in the RDATA part cannot be
treated transparently, as the compression pointers are only
...
... context of a DNS message. Transparently
copying the RDATA into a new DNS message would cause the compression
...
... To avoid such corruption, servers MUST NOT compress domain names
embedded in the RDATA of types that are class-specific or not well-
known. This requirement ...
... RR types that contain domain names
within their RDATA MUST NOT allow the use of name compression for
those names, and SHOULD explicitly state ...
... RDATA>" and "[<class>] [<TTL>] <type> <RDATA>" forms of
[RFC1035] to both be unambiguously parsed.
...
... RFC1035] to both be unambiguously parsed.
The RDATA section of an RR of unknown type is represented as a
sequence of white space separated words as follows:
...
... token \# (a backslash immediately followed by a hash
sign), which identifies the RDATA as having the generic encoding
defined herein rather than a traditional type-specific encoding ...
...
An unsigned decimal integer specifying the RDATA length in octets.
Zero or more words of hexadecimal data encoding ...
...
Zero or more words of hexadecimal data encoding the actual RDATA
field, each containing an even number of hexadecimal digits.
...
... field, each containing an even number of hexadecimal digits.
If the RDATA is of zero length, the text representation contains only
the \# token and the single zero representing the length.
...
... using the above generic representations for the type, class and/or
RDATA, which carries the benefit of making the resulting master file
portable to servers where these types are unknown. Using the generic
representation for the RDATA ...
... RDATA, which carries the benefit of making the resulting master file
portable to servers where these types are unknown. Using the generic
representation for the RDATA of an RR of known type can also be
useful in the case of an RR ...
... depending on a version, protocol, or similar field (or several)
embedded in the RDATA when such a field has a value for which no text
format is known, e.g., a LOC RR [RFC1876 ...
... RR of known type represented in the \# format is
effectively treated as an unknown type for the purpose of parsing the
RDATA text representation, all further processing by the server MUST
treat it as a known type and take into account any applicable type-
...
... to be compared for equality. Two RRs of the same unknown type are
considered equal when their RDATA is bitwise equal. To ensure that
the outcome of the comparison is identical whether the RR ...
... canonical form, domain names embedded in the
RDATA are converted to lower case.
The downcasing is necessary to ensure the correctness of DNSSEC
signatures ...