multi-record DNS monitoring

[mrogers-9898]

Howdy all,

I'd like to monitor DNS, but I've struck a minor problem with mutli-record DNS entries.

this example below is a MX check, with 1st and 2nd check's value.

mymaildomain.com MX 10 mymaildomain-com.p10.spamfilter.not
mymaildomain.com MX 20 mymaildomain-com.p20.spamfilter.not
mymaildomain.com MX 30 mymaildomain-com.p30.spamfilter.not
mymaildomain.com MX 40 mymaildomain-com.p40.spamfilter.not
----------------------------------------------
mymaildomain.com MX 30 mymaildomain-com.p30.spamfilter.not
mymaildomain.com MX 40 mymaildomain-com.p40.spamfilter.not
mymaildomain.com MX 10 mymaildomain-com.p10.spamfilter.not
mymaildomain.com MX 20 mymaildomain-com.p20.spamfilter.not

notice that the details are actually the same, just returned in a different order?

So could I please get some input on whether I should I use a script to query then sort rather than

net.tcp.dns.query[8.8.8.8, mymaildomain.com, MX]

or should my trigger process the value better than

net.tcp.dns.query[8.8.8.8, mymaildomain.com, MX].change(0)}>0

[mrogers-9898]

I've changed my item from

net.tcp.dns.query[8.8.8.8, mymaildomain.com, MX]

to

system.run[dig +short mymaildomain.com MX | sort]

and this seems to have done the trick for me.