PowerDNS Recursor

The PowerDNS Recursor is a high-end, high-performance resolving name server. Utilizing multiple processors and supporting the same powerful scripting ability of the Authoritative Server, the Recursor delivers top performance while retaining the flexibility modern DNS deployments require.

Prerequisite

1. Edit the configuration file in /etc/powerdns/recursor.conf and set the values as follows:

webserver=yes
api-key=<api key>            # only available since ver 4.0
webserver-readonly=yes       # default no

2. Add the api-key and serverid in auto-monitoring.yaml file in /opt/opsramp/agent/conf/app/metrics/powerdnsrec
3. For Virtual machines, install the Linux agent.

Configuring the credentials

Configure the credentials in the directory /opt/opsramp/agent/conf/app.d/creds.yaml

powerdnsrecursor:
- name: powerdnsrecursor
  user: <username>
  pwd: <Password>
  encoding-type: plain
  labels:
    key1: val1
    key2: val2
  

Configuring the application

Virtual machine

Configure the application in the directory /opt/opsramp/agent/conf/app/discovery/auto-detection.yaml

- name: powerdnsrecursor
  instance-checks:
    service-check:
      - pdns-recursor
    process-check:
      - pdns-recursor
    port-check:
      - 8082
  

Docker environment

Configure the application in the directory /opt/opsramp/agent/conf/app/discovery/auto-container-detection.yaml

- name: powerdnsrecursor
  container-checks:
    image-check:
      - powerdns
    port-check:
      - 8082
  

Kubernetes environment

Configure the application in config.yaml

- name: powerdnsrecursor
  container-checks:
    image-check:
      - powerdns
    port-check:
      - 8082
  

Validate

Go to Resources under the Infrastructure tab to check if your resources are onboarded and the metrics are collected.

Supported metrics