What It Covers
- Cloudflare DNS record operations
- BIND support for self-hosted authoritative DNS
- Route53/API-backed provider model where configured
- Fleet-aware DNS workflows for distributed infrastructure
One Operational Surface for Mixed DNS Estates
Infrastructure often spans provider-hosted DNS and self-hosted zones. One-Click keeps the workflow consistent while preserving provider-specific capabilities underneath.
Cloudflare Remains an External Authority
One-Click does not replace Cloudflare. It uses the provider API as an automation target, leaving the Cloudflare zone and account authoritative.
Credentials Stay Operational, not in the Website
The documentation explains the configuration model but the website package contains no API token or account secret.
Useful Alongside Edge and NAT Workflows
Cloudflare DNS pairs naturally with HAProxy edge publishing, public sites and services that live behind private NAT infrastructure.