Right. Cname does not cross classes.
In original DNS, class was incoherently sometimes an attribute of zone data and
sometimes a namespace selector. In modern DNS it is coherently always the
latter.
On July 5, 2015 8:17:03 AM GMT+01:00, Ray Bellis <r...@bellis.me.uk> wrote:
>
>
>On 05/07/2015 01:35, Andrew Sullivan wrote:
>
> > Classes don't work in the general case, because CNAME (and following
> > it, DNAME) is class-independent. This is arguably a bug in the
> > protocol, but it's a fact nevertheless. As a result, different
> > classes aren't really different namespaces.
>
>Andrew,
>
>Can you please elaborate on what you mean there?
>
>Sure, CNAME is *defined* for all classes, but AFAIK there's no way to
>"jump" out of one class into another using a CNAME. If you've queried
>in class FOO and see a CNAME then the resolution of the target of the
>CNAME should continue in class FOO.
>
>RFC 1034 §3.6.2:
>
>"CNAME RRs cause special action in DNS software. When a name server
>fails to find a desired RR in the resource set associated with the
>domain name, it checks to see if the resource set consists of a CNAME
>record with a matching class. If so, the name server includes the CNAME
>
>record in the response and restarts the query at the domain name
>specified in the data field of the CNAME record."
>
>kind regards,
>
>Ray
>
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
