On Wed, Mar 16, 2016 at 01:36:21AM +0000, Ted Lemon wrote: > it might be worth anticipating whether an NXDOMAIN for class=X should also > result in an NXDOMAIN answer for the same name with class Y, where Y != X. >
FWIW, I believe that, according to the matching rules in STD 13, NXDOMAIN is class-bound. This is in fact related to the argument about how the class selector fails to do what we'd have needed it to: if you ask a name server that serves two different classes for the same name about that name, it will need to figure out which class you are asking about before it can start the label-by-label matching. There is no guarantee that there's an answer in every class for a name that is in one class. (If there were, the DNS would be broken today: the root servers won't give you delegation information about non-IN classes, as far as I can tell.) Best regards, A -- Andrew Sullivan a...@anvilwalrusden.com _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
