On 05/07/2015 18:16, Evan Hunt wrote: > On Sun, Jul 05, 2015 at 10:44:40AM -0400, Andrew Sullivan wrote: >> Imagine the alternative-resolution class FAKE. In the IN class, >> example.com has a DNAME entry pointing to example.net. What should >> happen when someone performs a query for QNAME localentry.example.com, >> TYPE AAAA, and CLASS FAKE? > > What *should* happen, IMHO, is the DNAME shouldn't come into consideration > because it only exists in class IN. localentry.example.com/FAKE/AAAA is in > a different namespace entirely, and a query for it should never reach the > example.com/IN zone.
I agree. I very strongly suspect that the omission of explicit QCLASS matching in DNAME is a simple omission that none of us caught at the time rather than a deliberate attempt to make DNAME class independent. Ray _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
