compression
Click on the red underlined text to get to the source
... RDATA of RRs of known type, except for changes
due to compression or decompression where allowed by section 4 of
this memo. In particular, the character case of domain names that
...
... Domain Name Compression ...
...
RRs containing compression pointers in the RDATA part cannot be
treated transparently, as the compression ...
... compression pointers in the RDATA part cannot be
treated transparently, as the compression pointers are only
meaningful within the context of a DNS ...
... copying the RDATA into a new DNS message would cause the compression
pointers to point at the corresponding location in the new message,
which now contains unrelated data. This would cause the compressed
...
... The specifications of a few existing RR types have explicitly allowed
compression contrary to this specification: [RFC2163] specified that
compression ...
... compression contrary to this specification: [RFC2163] specified that
compression applies to the PX RR, and [RFC2535] allowed compression ...
... NXT RRs records. Since this specification disallows
compression in these cases, it is an update to [RFC2163] (section 4)
...
... SRV RR
in [RFC2782] prohibits compression, [RFC2052] mandated it, and some
servers following that earlier specification are still in use).
...
... domain names
within their RDATA MUST NOT allow the use of name compression for
those names, and SHOULD explicitly state that the embedded domain
names ...
... by the server MUST
treat it as a known type and take into account any applicable type-
specific rules regarding compression, canonicalization, etc.
...
... DNSSEC
signatures when case distinctions in domain names are lost due to
compression, but since it requires knowledge of the presence and
position of embedded domain names, it cannot be applied to unknown
...
... canonical form of RR types
where compression is allowed, and for continued interoperability with
existing implementations that already implement the [RFC2535 ...