dns-ops

Name: dns-ops
Availability: InStock
Author: cogni-dao

Automates Cloudflare zone setup, apex records, node decommissioning, and protected-record safety via scripts.

4|5|Updated Nov 5, 2025

Search Tags:#automation #infrastructure #cloudflare #dns #ops #node-management #env-dns

Ready to run

npx skills add https://github.com/cogni-dao/cogni --skill dns-ops

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

One-time Cloudflare zone setup
Provisioning the env apex DNS record
Decommissioning a purged node DNS record
Protected-record safety: never modify zone apex, www, or MX records
Catalog-driven reconciliation ensures per-node DNS updates on flight

Quick Start

Run the initial Cloudflare zone setup and env apex provisioning once, then rely on the automated reconciliation to manage per-node DNS updates.

Frequently Asked Questions about dns-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate one-time Cloudflare zone setup for multi-node infrastructure?▼

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.

What is catalog-driven DNS reconciliation for node management?▼

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.

How do I decommission a purged node DNS record safely?▼

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.

When do I need to manually manage DNS records instead of relying on automation?▼

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.

What protected DNS records should I never modify during node decommissioning?▼

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.

Does this DNS ops approach work without hand-setting individual node records?▼

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.