BLAZINGFAST — DNS ZONES, RECORDS AND TEMPLATES
Reviewed: 5 October 2026. Setup: 00-index.txt.
Production release: SDK/CLI 0.1.17; contract 2026-10-07.1. Check GET /v1/version and GET /v1/capabilities before using optional workflow features. Strict response validation is enforced.

PURPOSE
Host authoritative DNS zones, edit records and reuse saved templates. Creation
does not register a domain or switch its registrar nameservers.

PUBLIC API
GET/POST /v1/dns/zones: list/create. POST accepts name and at most one source:
templateId, zoneFile text or records array; no source means an empty zone.
dryRun: true validates/previews without creating or reserving a zone.
GET/DELETE /v1/dns/zones/{name}; records and records/simple endpoints.
GET/POST /v1/dns/templates and template detail/update/delete endpoints.
Platform apex NS and SOA stay managed; an existing zone is not overwritten.
Permissions: dns.read / dns.write and an eligible active DNS service.

CLI
bf dns zone list
bf dns template list
bf dns record list example.com
Creation examples, only after reviewing the intended zone:
bf dns zone create example.com --empty --request-key dns-empty-001
bf dns zone create example.com --template TEMPLATE_NAME --request-key dns-template-001
bf dns zone create example.com --json-file records.json --dry-run --request-key dns-preview-001
bf dns zone create example.com --json-file records.json --request-key dns-create-001
Sources are mutually exclusive. Files are read locally, not fetched by URL.
records.json is an array of name/type/ttl/values record sets, not a full request.

MCP
Hosted: list_dns_zones, list_dns_records, list_dns_templates, get_dns_template,
preview_dns_zone_create, request_dns_zone_create, request_dns_record_set/delete,
request_dns_zone_delete. Preview and creation need different request keys.
Local: bf_dns_zone_list/show, bf_dns_record_list; opt-in bf_dns_zone_create,
bf_dns_record_set/delete, bf_dns_zone_delete. Local MCP does not expose templates,
file import or dry-run preview tools; use CLI/API for those workflows.

LIMITS AND SAFETY
Imports: 200 record sets, 50 values/set, TTL 1-86400 seconds, 100000 zone-file
characters. Hosted MCP import arguments also have a 48000-byte cap; UserAPI total
write requests are capped at 256 KiB. No $INCLUDE/$GENERATE or remote file fetch.
Read and review full existing/new values; append and replace have different effects.
Only the owning account/project can manage its zones. Legacy ns1/ns2 delegation
does not automatically make modern panel DNS edits authoritative; use the offered
nameserver fix after checking the zone. DNSSEC controls live under domain management.