DNS & Cloudflare

Manage BIND and API-backed DNS providers such as Cloudflare from One-Click without embedding provider secrets into site content.

The DNS workflow supports self-hosted BIND and API-backed providers. Cloudflare is a first-class provider target for operators who want DNS changes to follow the same guided One-Click workflow as the rest of their infrastructure.

Open DNS Management

one-click --dns

Cloudflare Credentials

Use scoped API tokens instead of global account credentials. Limit the token to the zones and DNS permissions that One-Click needs. Keep provider tokens secure on the machine that manages DNS. Do not put credentials in public site files, shared backups or published examples.

BIND

For BIND-backed environments, One-Click can manage zone creation and synchronisation/replication workflows across suitable Fleet nodes. Keep authoritative zone ownership explicit and validate configuration before reload.

DNS Cutover During Workload Movement

For external Fleet import/export, complete workload validation before changing authoritative records. This keeps application movement reversible and prevents DNS from hiding a failed destination deployment.