Ad Widget

Collapse

Zabbix Unbound DNS monitoring

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • eansp
    Junior Member
    • Aug 2017
    • 11

    #1

    Zabbix Unbound DNS monitoring

    I am having a strange situation where I have 8 DNS servers that are all successfully running Unbound DNS version 1.4.20.

    My Zabbix Server Version is 3.0.10
    All 8 DNS servers have Centos 7, and Zabbix Agent 3.0.10 installed.

    Only 1 server is able to monitor Unbound using the following Template: Zabbix Share Unbound.

    The other 7 servers show the following message from the zabbix server log file (this happens for all the items within the template except net.dns) :
    Code:
    26188:20171102:150828.689 item "hostnameB:unbound.histogram[000001.000000.to.000002.000000]" became not supported: Unsupported item key.
    I decided to just work with 2 servers; the only working one, and a non-working, to compare and contrast.

    What I have tried:

    Working DNS Server:
    Code:
    zabbix_get -s x.x.x.106 -k unbound.type[AAAA]
    Result was successful returning a value of 090814543. This performed from the Zabbix Server.

    Non-working DNS Server:
    Code:
    zabbix_get -s x.x.x.126 -k unbound.type[AAAA]
    Result was ZBX_NOTSUPPORTED: Unsupported item key. This was performed from the Zabbix Server.

    The template has the items configured for Passive checks so I made sure that 10050 was listening:

    Working netstat -pnlt | grep ':10050':
    Code:
    tcp        0      0 0.0.0.0:10050           0.0.0.0:*               LISTEN      29736/zabbix_agentd
    Non-Working netstat -pnlt | grep ':10050':
    Code:
    tcp        0      0 0.0.0.0:10050           0.0.0.0:*               LISTEN      24031/zabbix_agentd
    Verified the hostname in zabbix_agentd.conf matched the hostname configured in the GUI.

    Verified the Server is configured to the correct IP address in zabbix_agentd.conf and the GUI host.

    Verified the ListenPort was 10050 in zabbix_agentd.conf and the GUI host.

    Restarted the Zabbix Agent.

    Deleted the host in the GUI, and created a Full Clone of the working host.

    Deleted the host (again), and recreated from scratch.

    I'm out of ideas of what the problem could be, and I've been working on it for a couple of days now. Any help would be appreciated. If I need to provide configuration files or screenshots for the working and non-working DNS servers, I can.
  • kaspars.mednis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2017
    • 349

    #2
    At first quick look i see sudoers config in this template



    Code:
    Defaults:zabbix !requiretty
    zabbix ALL = NOPASSWD: /usr/sbin/unbound-control

    have you added all userparameters to zabbix_agentd.conf ?
    have you made adjustments to sudoers on all servers ?

    Regards,
    Kaspars

    Comment

    • eansp
      Junior Member
      • Aug 2017
      • 11

      #3
      Thank you for the assistance, I forgot to add the userparameter_unbound.conf to /etc/zabbix/zabbix_agentd.d.

      Comment

      Working...