mcpField
B
BIND 9 AIops

BIND 9 AIops

Local
github.com/AIops-toolsCloud & Infra0Updated 3d ago
Repository

About BIND 9 AIops

BIND 9 AIops is a governed MCP server and CLI for BIND 9 DNS operators. It uses fixed-argument BIND utilities for checks and guarded operations, with audited calls and explicit reporting of uncertain outcomes.

Key features

  1. 01服务与区域状态检查
  2. 02配置和已加载区域验证
  3. 03DNSSEC 与签名状态检查
  4. 04DNS 查询及主从 SOA 比对
  5. 05受控区域操作与结果标记
  6. 06调用审计与预算控制

Use cases

  1. 01验证 BIND 配置和区域加载情况
  2. 02排查 DNSSEC、查询及传输问题
  3. 03比较主从 DNS 区域序列号
  4. 04在确认保护下执行区域操作

MCP support

它提供 23 个 MCP 工具及对应命令行操作，用于 BIND 9 DNS 运维。每次调用均经审计；写操作可预演并确认，结果不确定时会明确标记。

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "aiops-tools-bind9-aiops": {
      "command": "uvx",
      "args": [
        "bind9-aiops"
      ]
    }
  }
}
Run commanduvx bind9-aiops

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypibind9-aiops0.2.1

Tools

23

Saved tool list · updated 3d ago

ParameterTypeRequiredDescription
targetanyNo

Details

From the project README

BIND 9 AIops

Governed BIND 9 DNS operations with 23 MCP tools and corresponding CLI commands. It executes rndc, named-checkconf and dig as fixed argument lists without a shell. Every call is audited and budgeted by the bundled governance harness.

What it checks

  • Named service and zone status from rndc.
  • Configuration and loaded-zone validation with named-checkconf -z.
  • DNSSEC validation mode.
  • Zone DNSSEC signing, managed-key and serve-stale status; running zone configuration where enabled.
  • Recursive fetch-limit hits, DNSSEC trust anchors, DNS TCP timeouts and per-zone signing progress.
  • DNS queries with their actual DNS response code.
  • Queries against a selected secondary server.
  • Guarded secondary retransfer and single-zone NOTIFY resend.
  • Primary and secondary SOA serial comparison. A failed or unparseable query returns null, never a fabricated zero or match.
  • bind_diagnose_zone keeps individual probe failures visible.

Setup from source

Requires Python 3.11+, uv, and BIND 9 command utilities on the operator host. Run uv sync --dev, uv run bind9-aiops init, then uv run bind9-aiops doctor. A manual ~/.bind9-aiops/config.yaml can specify paths and a DNS server:

targets:
  - name: local
    server: 127.0.0.1
    dns_port: 53
    rndc_config: /etc/bind/rndc.conf
    named_config: /etc/bind/named.conf
    timeout: 10

Use uv run bind9-aiops diagnose example.org or uv run bind9-aiops compare-soa example.org 192.0.2.2. The MCP entry point is uv run bind9-aiops-mcp. The process account needs access to its rndc key file and BIND config, but no elevated shell is given to the agent.

Scope and verification

reload-zone, refresh-zone, flush-name, retransfer-zone and notify-zone support dry-run and two CLI confirmations. RNDC command acceptance does not prove a queued zone reload or transfer completed, so these writes report outcomeUnknown; a lost command response does too. No safe undo exists for a cache flush, retransfer, NOTIFY delivery or externally edited zone file. Zone-file editing, DNSSEC key changes and global service restarts remain outside this release. See verification. Missing features and live-environment feedback are welcome as issues or PRs.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.