domain name
Click on the red underlined text to get to the source
... due to compression or decompression where allowed by section 4 of
this memo. In particular, the character case of domain names that
are not subject to compression ...
... Domain Name Compression ...
... name to be corrupted.
To avoid such corruption, servers MUST NOT compress domain names
embedded in the RDATA of types that are class ...
...
Future specifications for new RR types that contain domain names
within their RDATA MUST NOT allow the use of name compression ...
... compression for
those names, and SHOULD explicitly state that the embedded domain
names MUST NOT be compressed.
As noted in [RFC1123 ...
... comparison rules.
This implies that embedded domain names, being included in the
overall bitwise comparison, are compared in a case-sensitive manner.
...
...
As a result, when a new RR type contains one or more embedded domain
names, it is possible to have multiple RRs owned by the same name
that differ only in the character case of the embedded domain
name ...
... domain
names, it is possible to have multiple RRs owned by the same name
that differ only in the character case of the embedded domain
name(s). This is similar to the existing possibility of multiple TXT
records differing only in character case, and not expected to cause
any problems in practice.
...
... RFC2535]
(section 8.1). In that canonical form, domain names embedded in the
RDATA are converted to lower case.
...
...
The downcasing is necessary to ensure the correctness of DNSSEC
signatures when case distinctions in domain names are lost due to
compression, but since it requires knowledge of the presence and
...
... compression, but since it requires knowledge of the presence and
position of embedded domain names, it cannot be applied to unknown
types.
...
... set of such previously published RR types that contain embedded
domain names, and whose DNSSEC canonical form therefore involves
...
... 3597prop), the canonical form is such
that no downcasing of embedded domain names takes place, and
otherwise identical to the canonical form specified in [RFC2535 ...
... Mockapetris, P., "Domain Names - Concepts and Facilities", STD 13, RFC 1034std13, November 1987. ...
... Mockapetris, P., "Domain Names - Implementation and Specifications", STD 13, RFC 1035std13, November 1987. ...
... Eastlake, D., "Domain Name System Security Extensions", RFC 2535(-> 4035prop | 4034prop | 4033prop), March 1999. ...
... Eastlake, D., Brunner-Williams, E. and B. Manning, "Domain Name System (DNS) IANA Considerations", BCP ...
... Davis, C., Vixie, P., Goodwin, T. and I. Dickinson, "A Means for Expressing Location Information in the Domain Name System", RFC 1876exp, January 1996. ...
... Vixie, P., Ed., Thomson, S., Rekhter, Y. and J. Bound, "Dynamic Updates in the Domain Name System (DNS UPDATE)", RFC 2136prop ...