During report on bind-utils for RHEL9, it were found dig plugin fails to correctly match name looked for. It depends on wrong assumption that each record type is delimited by tab. That is not necessary the case. https://github.com/nagios-plugins/nagios-plugins/pull/745 Reproducible: Always Steps to Reproduce: 1. dnf install bind-utils nagios-plugins dnsmasq 2. echo 'address=/12-345678example.com/172.23.75.243' > /etc/dnsmasq.d/long.conf 3. systemctl restart dnsmasq 4. /usr/lib64/nagios/plugins/check_dig -l lxos-monitoring-probe.12-345678example.com -a 172.23.75.243 Actual Results: # /usr/lib64/nagios/plugins/check_dig -l lxos-monitoring-probe.12-345678example.com -a 172.23.75.243 DNS WARNING - 0.012 seconds response time (Server not found in ANSWER SECTION)|time=0.011995s;;;0.000000 Expected Results: $ ./check_dig -l lxos-monitoring-probe.12-345678example.com -a 172.23.75.243 -t 600 DNS OK - 0,044 seconds response time (lxos-monitoring-probe.12-345678example.com. 10 IN A 172.23.75.243)|time=0,044113s;;;0,000000 Caused by commit https://github.com/nagios-plugins/nagios-plugins/commit/cbdfd8a9bd83ed22dc6e9b3e5104ed81de388596
There are other bugs in nagios check_dig plugin in 2.4.8 (regardless of OS; I see them on CentOS 7). I just submitted these this morning: - check_dig: 2.4.8 broke monitoring of the root zone (.) https://github.com/nagios-plugins/nagios-plugins/issues/760 - check_dig: 2.4.8 not checking for record type in the answer https://github.com/nagios-plugins/nagios-plugins/issues/761
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.