fix it?

[ghost]

Do you care adopting this for the latest Bind9.16?

The only things which seems to work in it is the bind.discoverzones.

[ghost]

Ok I get it working, there are some issues tho. First off the counters should default to zero.

Because currently if there were no query for a certain type of record like NS here:

/usr/zabbix4/bin/zabbix_get -s 1.2.3.4 -p10050 -k bind.incounter[NS]
ZBX_NOTSUPPORTED

You will get notsupported like something would be broken but it isn't. There was simply no NS query before. After I do an NS query against that bind it starts working.

The discoverzones finds tons of useless reverse zones, because of this over 1000 zabbix entries were created. As a solution for this I did the simple trick:

UserParameter=bind.discoverzones, echo '[t|{"data": ...}]}]'

[ghost]

So here is the problem the checks are all grayed out (it does nothing) because I assume that the required master item:

                    <master_item>
                        <key>bind.json</key>
                    </master_item>

is missing. This key should be: bind.json and other subzones bind.jsonzone[domain.lan] for example.
You don't have this key anywhere in your zabbix_agentd.conf so where is it coming from and what does it do.

I have tried to do:

UserParameter=bind.json,echo 'bindstats.json'

just what the hell is this parameter should do. I doubt it's pointing to a location on the remove fs.

[empereira]

hey @feraldruid22,

Were you able to fix this issue?

[zeduperes]

I have the same issue, Did you solve the problem ?