Cloudflare DNS

Overview

Use this skill to make Cloudflare DNS changes deliberately: identify the real product path, inspect existing records first, apply idempotent changes, and verify against Cloudflare or authoritative DNS instead of guessing.

Hard Rules

• Do not overwrite or delete DNS records until you have listed the existing records for the exact hostname and type.
• Default to dry-run planning unless the user explicitly asks you to apply the change.
• Preserve user-provided record values literally: type, name, content, priority, TTL, proxied state, and comments.
• Treat Cloudflare Pages, Workers Custom Domains, Workers Routes, and ordinary DNS as different workflows.
• For production domains, verify after write with the Cloudflare API and DNS queries. Prefer authoritative nameservers when available.
• Never print full API tokens. Report only whether CLOUDFLARE_API_TOKEN / CLOUDFLARE_ACCOUNT_ID are present.

Choose The Path