Dear Maintainer,

As a devops guy working on prometheus community stuff I would ask you to
upgrade the official debian 11 package for *prometheus-bind-exporter
(v0.4.0) *to latest stable release *v0.6.1*. It fixes a major bug that
blocks users working with bind v9.18.12+

What led up to the situation?
Upgrade to any bind version 9.18.12+ crashes every bind-exporter release below version 0.6.1.
The problem is an unmarshall value of negative xml files.

What exactly did you do (or not do) that was effective?
Upgrade to bind version v9.18.12+

What was the outcome of this action?
Unmarshall error of bind statistics channel output -> hence no valid metrics

What outcome did you expect instead?
Correct pars of bind xml output and output of metrics

For further information on fix, please check the project source of prometheus-exporter
https://github.com/prometheus-community/bind_exporter/releases/tag/v0.6.1

I am also affected by this bug on Debian bullseye (current old stable)
since bind9 has been updated to 1:9.16.50-1~deb11u1 from bullseye-security.

Here is the error message a get:

     juil. 29 23:11:24 club1.fr prometheus-bind-exporter[591]:
level=error ts=2024-07-29T21:11:24.570Z caller=bind_exporter.go:427
msg="Couldn't retrieve BIND stats" err="failed to unmarshal XML
response: strconv.ParseUint: parsing \"-1\": invalid syntax"

I am seeing this on stable too, with a supposedly fixed version:

bind_exporter, version 0.7.0 (branch: debian/sid, revision: 0.7.0-3)
  build user:       team+pkg-go@tracker.debian.org
  build date:       20240312-13:14:23
  go version:       go1.22.1
  platform:         linux/amd64
  tags:             unknown

BIND 9.18.28-1~deb12u2-Debian (Extended Support Version) <id:>

Aug 09 09:52:34 attila bind_exporter[1800625]: time="2024-08-09T09:52:34+02:00" level=error msg="Couldn't retrieve BIND stats: failed to unmarshal XML response: strconv.ParseUint: parsing \"-1\": invalid syntax" source="bind_exporter.go:391"

Control: notfound -1 0.7.0-3