Misfeature of 9.4.2 named-checkzone

[Chris Thompson]

There is an infelicity (I hesitate to call it a bug) in the 9.4.2
version of named-checkzone.

When using the -D option, the 9.3.4 named-checkzone used to output
each RRset in a normalised order, e.g. A records with the same name
were in ascending order.

When applied to a zone file written by BIND, that's apparently still
true in 9.4.2. But if one applies named-checkzone to a messily ordered 
input zone file with the default output style (-F text -s full) then
each RRset retains the order of the component RRs in the input.

This makes it more awkward to compare zone files for equality (e.g. to
answer the question "has any of this incremental update stuff caused
zone content drift?"). Of course, one can always sort the output files
from named-checkzone before comparing them, but this used not to be
necessary.

-- 
Chris Thompson
Email: cet1 at cam.ac.uk