Automates Cloudflare zone setup, apex records, node decommissioning, and protected-record safety via scripts.
npx skills add https://github.com/cogni-dao/cogni --skill dns-ops
Please help me install this Agent Skill. Skill: dns-ops Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/dns-ops Command: npx skills add https://github.com/cogni-dao/cogni --skill dns-ops
Node DNS is automated and catalog-driven (do NOT hand-set it); this surface handles genuinely manual tasks: one-time Cloudflare zone setup, the env apex record, decommissioning a purged node DNS record, and protected-record safety.
Run the initial Cloudflare zone setup and env apex provisioning once, then rely on the automated reconciliation to manage per-node DNS updates.
High-intent search queries and answers about installing and using this skill.
Cloudflare zone setup for multi-node infrastructure is automated by running initial provisioning scripts to configure the zone and establish the environment apex record. After this one-time setup, catalog-driven reconciliation manages per-node DNS updates automatically.
Catalog-driven DNS reconciliation is an automated process that ensures per-node DNS updates occur dynamically during flight. It uses scripts like reconcile-node-dns.sh to perform idempotent updates, preventing the need to hand-set node DNS records manually.
To decommission a purged node DNS record safely, use the specific decommissioning scripts provided. These scripts remove the targeted records while enforcing protected-record safety to prevent accidental modification of zone apex, www, or MX records.
Manual DNS management is needed for one-time operations like Cloudflare zone setup, provisioning the env apex record, and decommissioning purged node records. Per-node DNS is fully automated and catalog-driven, so day-to-day node DNS should never be hand-set.
During node decommissioning, you should never modify the zone apex, www, or MX records. The decommissioning process includes built-in protected-record safety to safeguard these critical DNS entries from accidental changes.
Yes, this approach works without hand-setting individual node records by relying on catalog-driven reconciliation. You only manually run the one-time zone setup and env apex provisioning, after which automated scripts like reconcile-node-dns.sh handle all per-node updates idempotently.
zeenie-aiManage Cloudflare DNS, zones, and analytics via the cf CLI and GraphQL API.
ClawLink-HQManage Cloudflare zones, DNS records, workers, and firewall rules via the Cloudflare API.
cogni-daoGuide OpenBao+ESO and GitHub environment secrets for node-template deployments.
mattstyles333Manage Cloudflare DNS records via API-driven bash script.
