Skill

dns-management

Use this skill when the user asks to "manage DNS", "add a DNS record", "update DNS", "delete a DNS record", "create an A record", "set up a CNAME", "configure MX records", "list DNS records", "check DNS settings", or any task involving Cloudflare DNS zones or records.

npx claudepluginhub pzharyuk/ai-claude-plugins --plugin cloudflare-extended

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use the `cloudflare-extended` MCP server tools to manage DNS records for the user's Cloudflare zones.

Supporting Assets

references/dns-record-types.md

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 21, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Cloudflare DNS Management

Use the cloudflare-extended MCP server tools to manage DNS records for the user's Cloudflare zones.

Workflow

Listing records

If the user hasn't specified a zone, call cf_list_zones to show available domains and ask which one to work with.

Call cf_list_dns_records with the resolved zone_id. Use optional type or name filters to narrow results.

Present records clearly: type, name, content, TTL, and whether proxied.

Creating a record

Confirm: record type, name (fully qualified or relative), content, TTL (default: 1 = auto), and whether to proxy.

For MX records, also confirm priority.

Call cf_create_dns_record. Confirm success and show the new record ID.

Updating a record

If no record ID is known, list records first to find the right one.

Ask the user which fields to change.

Call cf_update_dns_record with only the changed fields.

Deleting a record

Always show the record to be deleted and ask for explicit confirmation before proceeding.

Call cf_delete_dns_record.

Confirm deletion.

Record Type Reference

See references/dns-record-types.md for content format requirements per record type.

Best Practices

Proxied records (orange cloud) route traffic through Cloudflare — appropriate for web traffic (A, AAAA, CNAME to web servers).

Non-proxied records (grey cloud) expose the origin IP — use for mail servers, FTP, SSH, or services that can't be proxied.

TTL of 1 (auto) is fine for most records. Use longer TTLs only for rarely-changed records.

Always confirm before deleting — DNS deletions can cause immediate outages.