cloudflare-dns

Name: cloudflare-dns
Availability: InStock
Author: MakerJackie

Configure Cloudflare DNS records and custom page domain bindings via API token.

1|Updated Feb 20, 2026

Search Tags:#automation #api #cloudflare #dns #pages #custom-domain

Ready to run

npx skills add https://github.com/makerjackie/jackie-skills-starter --skill cloudflare-dns-makerjackie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cloudflare-dns
Source: https://github.com/makerjackie/jackie-skills-starter/tree/main/skills/cloudflare-dns
Command: npx skills add https://github.com/makerjackie/jackie-skills-starter --skill cloudflare-dns-makerjackie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual, error‑prone steps of creating, updating, or deleting Cloudflare DNS records and binding custom domains to Cloudflare Pages, ensuring proper verification and minimal permission usage.

Core Features & Use Cases

Idempotent DNS Management: Reads existing records before making changes to avoid unintended overwrites.
Custom Domain Binding for Pages: Automates the addition of domains to Cloudflare Pages projects and syncs DNS accordingly.
Safety & Validation: Enforces token scope checks, prompts for missing permissions, and verifies changes with DNS lookups and HTTP requests.
Use Case: A developer needs to point app.example.com to a new Cloudflare Pages site while ensuring the DNS record is correctly proxied and verified.

Quick Start

Ask the skill to add an A record for 'example.com' pointing to '192.0.2.1' with proxy enabled.

Frequently Asked Questions about cloudflare-dns

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

FAQPage Schema

How do I automate Cloudflare DNS record creation without overwriting existing entries?▼

Automating Cloudflare DNS record creation safely requires reading existing records before applying changes. This idempotent approach prevents unintended overwrites by checking current configurations and verifying that additions or edits do not conflict with active zones.

What is the best way to bind a custom domain to Cloudflare Pages and sync DNS?▼

Binding a custom domain to Cloudflare Pages involves adding the domain to the Pages project and automatically syncing the required DNS records. This ensures the domain is correctly proxied and validated without manual record configuration errors.

Do I need specific API token permissions to manage Cloudflare DNS records and custom domains?▼

Yes, managing Cloudflare DNS records requires an API token with DNS edit and zone read permissions. For custom domain binding to Cloudflare Pages, the token must also include optional Pages edit permissions to fully automate the domain binding and sync process.

How can I verify Cloudflare DNS propagation after adding a new A or CNAME record?▼

Verifying Cloudflare DNS propagation after adding A, AAAA, or CNAME records involves performing DNS lookups and HTTP requests. This checks if the new records have resolved correctly across the zone and if the domain validation errors have been fixed.

Does this approach support editing TXT records for domain validation across Cloudflare zones?▼

Yes, this approach supports adding, editing, and deleting TXT records to manage domain validation across Cloudflare zones. It reads existing TXT records first to avoid overwrites and verifies propagation to fix domain validation errors effectively.