Cloudflare DNS Record

Deploys a single DNS record into an existing Cloudflare DNS zone. The component supports all 21 Cloudflare record types — simple types whose value is a content string (A, AAAA, CNAME, MX, NS, PTR, TXT, OPENPGPKEY) and structured types configured through a typed data block (CAA, CERT, DNSKEY, DS, HTTPS, LOC, NAPTR, SMIMEA, SRV, SSHFP, SVCB, TLSA, URI) — with optional Cloudflare proxy (orange-cloud) mode for A, AAAA, and CNAME records.

What Gets Created

When you deploy a CloudflareDnsRecord resource, Planton provisions:

• DNS Record — a cloudflare_dns_record resource in the specified zone, configured with the given type, value (content or a data block), TTL, proxy setting, tags, settings, and optional priority and comment

Prerequisites

• Cloudflare credentials configured via environment variables or Planton provider config
• An existing Cloudflare DNS zone — either the zone ID as a literal string or a deployed CloudflareDnsZone resource to reference
• Appropriate permissions — the API token must have DNS edit access for the target zone

Quick Start

Create a file dns-record.yaml:

apiVersion: cloudflare.planton.dev/v1
kind: CloudflareDnsRecord
metadata:
  name: my-record
spec:
  zoneId:
    value: 0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d
  name: www
  type: A
  content: "203.0.113.50"
  proxied: true

Deploy:

planton apply -f dns-record.yaml

This creates a proxied A record for www in the specified zone, routing traffic through Cloudflare's CDN and WAF.

Configuration Reference

Required Fields

Exactly one of content or a data block is required and must match the type.

Value Fields

Optional Fields

Zone ID Reference

The zoneId field accepts either a literal value or a cross-resource reference:

spec:
  zoneId:
    valueFrom:
      name: my-zone

When using valueFrom, the kind defaults to CloudflareDnsZone and the fieldPath defaults to status.outputs.zone_id, so only the resource name is required.

Examples

MX Record for Mail Delivery

apiVersion: cloudflare.planton.dev/v1
kind: CloudflareDnsRecord
metadata:
  name: mail-mx-record
spec:
  zoneId:
    value: 0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d
  name: "@"
  type: MX
  content: aspmx.l.google.com
  priority: 1
  ttl: 3600
  comment: "Google Workspace primary"

SRV Record (structured data)

apiVersion: cloudflare.planton.dev/v1
kind: CloudflareDnsRecord
metadata:
  name: sip-srv-record
spec:
  zoneId:
    valueFrom:
      name: prod-zone
  name: "_sip._tcp"
  type: SRV
  data:
    srv:
      priority: 10
      weight: 5
      port: 5060
      target: sip.example.com

CAA Record (structured data)

apiVersion: cloudflare.planton.dev/v1
kind: CloudflareDnsRecord
metadata:
  name: caa-record
spec:
  zoneId:
    value: 0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d
  name: "@"
  type: CAA
  data:
    caa:
      flags: 0
      tag: issue
      value: letsencrypt.org

Stack Outputs

After deployment, the following outputs are available in status.outputs:

Related Components

• CloudflareDnsZone — manages the parent DNS zone; its zone_id output can be referenced by this component via valueFrom
• CloudflareR2Bucket — may use DNS records for custom domain access
• CloudflareWorker — commonly paired with DNS records pointing to Worker routes
• CloudflareLoadBalancer — load balances traffic across origins, often configured alongside DNS records