check_dns 2.3.3 (bundled with 5.20) misses option -q while RPM version 2.3.3 has it included

[pbiering]

Is there a packaging/bundling problem?

check_dns reports same version, but has different features, the OMD one looks like from 2008 while the RPM based one is from 2018

OMD 5.20:

/opt/omd/versions/default/lib/monitoring-plugins/check_dns -h
check_dns v2.3.3 (monitoring-plugins 2.3.3)
Copyright (c) 1999 Ethan Galstad <[email protected]>
Copyright (c) 2000-2008 Monitoring Plugins Development Team
        <[email protected]>
...

(missing option -q)

while from RPM nagios-plugins-dns-2.3.3-6.el8.x86_64:

/usr/lib64/nagios/plugins/check_dns -h
check_dns v2.3.3 (nagios-plugins 2.3.3)
Copyright (c) 1999 Ethan Galstad <[email protected]>
Copyright (c) 2000-2018 Nagios Plugin Development Team
...
 -q, --querytype=TYPE
    Optional DNS record query type where TYPE =(A, AAAA, SRV, TXT, MX, ANY)
    The default query type is 'A' (IPv4 host entry)
    BIND 9.11.x onwards supports both 'A' and 'AAAA', if you want both use 'ANY'
...

[sni]

OMD ships the https://www.monitoring-plugins.org/ while rhel uses nagios-plugins. Both projects having the same version is only a coincidence and might happen, since both share the same roots.

[pbiering]

Looks like related to monitoring-plugins/monitoring-plugins#894, while check_dns from Nagios plugins was extended, Monitoring plugins refer to use check_dig as replacement.

So I see some options

1. clearly mark check_dns as deprecated in OMD / Monitoring plugins
2. merge from Nagios plugins to be back on equal feature level even it should be phased out

[pbiering]

During evaluation/migration it turned out that check_dns cannot be 100% replaced by check_dig

• check_dns by default is using DNS servers configured in /etc/resolv.conf for a query and can be used for configuration of generic DND lookup checks
• check_dig by default is using DNS server 127.0.0.1 if not explicitly supplied via option -H and can only be used checking dedicated DNS servers