Skip to content

Conversation

@RincewindsHat
Copy link
Member

@RincewindsHat RincewindsHat commented Mar 8, 2025

Refactor check_dns for better maintainability.

Also integrates #1406

Suppose your provider uses RFC 2317 (or RFC 4183 for that matter). The output of nslookup could look like the following:
2.120.22.172.in-addr.arpa	canonical name = 2.0/26.120.22.172.in-addr.arpa.
2.0/26.120.22.172.in-addr.arpa	name = rajesh.intern.prauscher.de.
Without this filter, check_dns would check the string against "2.0/26.120.22.172.in-addr.arpa., rajesh.intern.prauscher.de." which will fail for obvious reasons.
In forward DNS, this is achieved in line 165, as nslookup will print the address separate from the CNAME-resolving.

Original commit by Patrick Rauscher ([email protected]), adapted
here.
@RincewindsHat RincewindsHat merged commit 75568a3 into monitoring-plugins:master Mar 9, 2025
7 checks passed
@RincewindsHat RincewindsHat deleted the refactor/check_dns branch March 9, 2025 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant