Heho, > Isn't the latter selection more constrained than the former, that is, > shouldn't an "All NS fulfill X" criterion lead to lower numbers than "at > least one NS fulfills X"?
I made the categories exclusive; Sorry if this was not clear. So: > > At least one NS is a CNAME and zone has more than one NS: What is missing in the description is "and not all NS are CNAMEs"; Sorry for that. I did that to separate "CNAME NS may break zone" from "there potentially is still a correctly configured NS"; Furthermore I split "All NS are CNAME" from "Only one NS and that is a CNAME" to separate out 'noise/small' zones with only one NS. The top one [At least one NS is a CNAME (Aggregate of the three distinct categories below)] is then the aggregate of the three distinct classes. With best regards, Tobias _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
