← Back to directory
N

Netdata BIND Query Server

Community
Inspect BIND DNS query statistics.
GitHub source repository ↗
★ 79.8k Stars Category · Other Very popular
20FMRS · D
Reliability
1/20
Security and permissions
6/20
Maintenance
12/20
Documentation
1/20
Setup experience
0/20

The source supports describing this as BIND DNS statistics test data within Netdata. It does not provide confirmed MCP tools, transport, installation instructions, or client support.

Read the FMRS scoring method →

This server path corresponds to a BIND query statistics test-data manifest in the Netdata repository. It records opcode, response-code, query-type, resolver, cache, zone-transfer, and view statistics. The supplied material does not document MCP tools, transport, client compatibility, or installation, so capabilities from other Netdata components must not be attributed to this server.

Tools

The tool list has not been reviewed yet.

Setup

The source provides no installation steps, launch command, or client configuration example.

Fit and risk

Best for

  • DNS or observability researchers analyzing BIND statistics manifests
  • Operators troubleshooting DNS behavior from existing statistics data

Not for

  • Users requiring confirmed MCP tool-call capabilities
  • Users needing live connections, DNS writes, configuration changes, or administrative operations
  • Users requiring verified Claude Desktop or other client compatibility

Required permissions

  • The source does not establish any required file, network, DNS-administration, or authentication permissions

Risks and side effects

  • This is a JSON statistics manifest under a testdata path; it does not establish an executable MCP interface
  • The timestamps and counters are historical and may not represent current DNS state
  • Capabilities described for the Netdata Agent, Cloud, or other components must not be attributed to this server

Troubleshooting

  1. Verify the target path is src/go/plugin/go.d/collector/bind/testdata/query-server.json
  2. Validate that the JSON is complete and has not been truncated or altered
  3. If MCP tools, transport, or client support are expected, obtain evidence for the corresponding server implementation or configuration

Use cases

Analyze BIND DNS query, response, and cache statistics
Inspect resolver latency, failures, timeouts, and zone-transfer data
Use DNS statistics as input for monitoring and observability research

Supported clients

Supported clients have not been confirmed yet.

More servers from this repository