named-checkzone -k check-names-fail kentlaw.edu junk
junk:13: ignoring out-of-zone data (600front)
junk:14: ignoring out-of-zone data (703front)
junk:15: ignoring out-of-zone data (723fix)
junk:16: ignoring out-of-zone data (749front)
junk:17: ignoring out-of-zone data (771back)
junk:18: ignoring out-of-zone data (775front)
junk:19: ignoring out-of-zone data (803front)
junk:20: ignoring out-of-zone data (823back)
junk:21: ignoring out-of-zone data (849back)
junk:22: ignoring out-of-zone data (97conf)
junk:66: gc._msdcs.kentlaw.edu: bad owner name (check-names)
junk:67: gc._msdcs.kentlaw.edu: bad owner name (check-names)
zone kentlaw.edu/IN: loading master file junk: bad owner name (check-names)

Note the following bug is fixed in 9.3.1 and the above command
becomes "named-checkzone -k fail kentlaw.edu junk" and it defaults
to warn as documented.

1727. [bug] named-checkzone: check-names support didn't match
documentation.

The usual way to address this is to create a seperate zone for
_msdcs.kentlaw.edu and set "check-names ignore;" for that zone.
That way you still detect errors outside of the AD namespace.

The "ignoring out-of-zone data" will be due to how you edited the
zone.

Reading all the messages from named would have shown you the exact
error "gc._msdcs.kentlaw.edu: bad owner name (check-names)".
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org