Type TXT, order irelevant

[puggan]

If a domain have 2 TXT-records, and one server returns them in one order, and the 2nd one return them in another order, they should still be ok?

Or are there a reason they are marked as missmatched?

[puggan]

There was one char different in one of the lines, so it should be a miss-match, but the output could be better, like:

• indent all lines equally, so they are comparable, of the two lines I needed to compare, only one of them hade a prefix " Received: ", so the one without a prefix was 12 chars off.
• if some of the rows are identical, hide them or otherwise mark them as uninteresting.

[puggan]

Partialy solved with PR 4

If the DNS-response have at least 2 rows, the there is a line-break between the header/prfix and the result, so that all results (dns and zone-file) start at the same position. (0 indentation).

But if zone-file has at least 2 rows and DNS-respone only have one row, the output is not changed, the header/predix still shares the line with the first result.

TODO:

• use seprate lines also in the case 1/2 mention above
• Show the number of results, if the zone-file has 49 rows, and the dns-result have 47, a row showing thus 2 numbers may be helpsome
• compare lines, and mark up lines that are same, either hide lines that are same, or prefix lines using symbols like "=" same, "+" missing in zone-file, "-" missing at dns