By: Tom Sydney Kerckhove <syd@cs-syd.eu>
Compare RRsets without regard to order Records within an RRset have no defined order (RFC 2181, section 5), so a resolver may return them in a different order on every query. A caching resolver hands out whatever order it happened to store, which changes each time the cache entry is refilled, so a TXT check on a name with more than one record failed intermittently. MX and NS already sorted both sides. Do the same for A, AAAA and TXT via a shared rrSetShouldBe. CNAME is left alone because a chain's order is meaningful.