ChatDNS

ChatDNS is a ChatArch DNS helper extracted from ChatTool. It provides a standalone chatdns CLI and importable Python API for DNS record management, DDNS updates, provider clients, IP detection, DNS-01 certificate automation, and MCP registration.

Commands

chatdns --help
chatdns list
chatdns --env work list --provider tencent
chatdns list --provider tencent --env work
chatdns records example.com
chatdns records test.example.com
chatdns set test.example.com -t A -v 1.2.3.4
chatdns delete test.example.com -t A -v 1.2.3.4 --yes
chatdns ip
chatdns cert apply -d '*.precision.example.com' -e admin@example.com --provider aliyun --cert-path precision
chatdns cert check '*.precision.example.com' --cert-path precision
chatdns cert manifest ./manifest.json

Supported providers in this release:

• Aliyun DNS
• Tencent Cloud DNSPod

Certificate management from the old chattool dns cert surface is now available as chatdns cert. It uses ACME DNS-01 validation and writes TXT records through the configured DNS provider. Treat live certificate issuance as an external side effect: test with --staging first and verify provider credentials before production use.

Configuration

ChatDNS reads provider credentials and defaults from environment / ChatEnv-compatible config fields:

• CHATDNS_PROVIDER (default DNS provider/channel: aliyun or tencent)
• CHATDNS_CERT_DIR (certificate storage directory; defaults to $CHATARCH_HOME/certs)
• ALIBABA_CLOUD_ACCESS_KEY_ID
• ALIBABA_CLOUD_ACCESS_KEY_SECRET
• ALIBABA_CLOUD_REGION_ID
• TENCENT_SECRET_ID
• TENCENT_SECRET_KEY
• TENCENT_REGION_ID

Active ChatEnv profiles are loaded automatically from $CHATARCH_HOME/envs (default: ~/.chatarch/envs). Use --env/-e to select a named provider profile, either globally before the command (chatdns --env work list -p tencent) or on DNS commands after the provider (chatdns list -p tencent -e work). Command-level --env/-e overrides the global value. chatdns cert apply keeps -e for email, so use --env work there.

Certificate roots use this precedence: explicit --cert-dir / Python cert_dir, then ChatEnv CHATDNS_CERT_DIR, then $CHATARCH_HOME/certs. Each certificate is stored at <registered-domain>/<cert-path>/; an omitted path uses default, collisions use numeric suffixes, and the same SAN set reuses its existing directory. ACME state stays under $CHATARCH_HOME/private/chatdns/acme, outside the certificate root.

See the certificate storage and creation rules for the generated file tree, permissions, multi-SAN renewal behavior, central managed-zone layout, and remote infrastructure boundary.

Provider aliases are registered through the package's chatenv.configs entry point as chatdns.config.

Development

python -m pytest -q
chatpypi build --project-dir .
chatpypi check --project-dir .
PYTHONPATH=src python -m chatdns.cli --help