CNAME
Click on the red underlined text to get to the source
... 2.1.3.
The actions when a source of synthesis owns a CNAME RR are changed to
mirror the actions if an exact match name owns a CNAME ...
... CNAME RR are changed to
mirror the actions if an exact match name owns a CNAME RR. This is
an addition to the words in RFC 1034std13 ...
... # we are looking for is the original QNAME in the query
# or a name we have followed due to a CNAME. If the name
# is original, set an authoritative name error in the
...
... instructions to "go to step 6":
If the data at the source of synthesis is a CNAME, and QTYPE
doesn't match CNAME, copy the CNAME ...
... If the data at the source of synthesis is a CNAME, and QTYPE
doesn't match CNAME, copy the CNAME RR into the answer section of
...
... CNAME, and QTYPE
doesn't match CNAME, copy the CNAME RR into the answer section of
the response changing the owner name to the QNAME, change QNAME to
...
... the response changing the owner name to the QNAME, change QNAME to
the canonical name in the CNAME RR, and go back to step 1.
...
...
This is essentially the same text in part 'a' covering the processing
of CNAME RRSets.
...
... discussed. The types covered are those that have proven to be the
most difficult to understand. The types are SOA, NS, CNAME, DNAME,
SRV, DS ...
... SRV RRSet at "*.example.", the answer section will reflect that
(be empty or a CNAME RRset).
...