Cloudflare DNS management
Coolify can create DNS records for application and service domains using a team's Cloudflare integration tokens. It matches each hostname to an accessible Cloudflare zone and points the record at the resource's server.
Add a token
- Create a Cloudflare API token with Zone > DNS > Edit and Zone > Zone > Read for the zones you want Coolify to manage.
- In Coolify, open Keys & Tokens > Integration Tokens and select New token, then choose Cloudflare in Provider.
- Enter a Token name, paste the API token, and select the DNS capability.
- Optionally enable Automatically configure DNS. New and edited domains are configured automatically when there is one unambiguous matching credential.
- Select Validate and add. Open the saved token's edit icon to review Domains this token can manage. Use Refresh zones after changing provider permissions, and Validate and save when editing credentials.
Integration tokens belong to a team. Add the token to the team that owns the resource. This token workflow is separate from configuring a proxy's DNS challenge for certificate issuance.
Manage a domain
Open an application's or service's Domains page and add the hostname, or change an existing domain to it. Coolify matches it to zones available through the team's tokens. With automatic DNS, Coolify creates the record; otherwise it opens the Configure DNS dialog for that server.
A clone of an application or service, and an application or service created through the API, also get a record for each domain in a zone with automatic DNS. A clone gets records only for the domains that the source does not use.
If a record already points elsewhere, automatic DNS replaces it only when Coolify created it and no other resource uses it. Otherwise the domain shows the conflict and the Configure DNS dialog opens. Review the existing value before using the replace action. Records created through this workflow show Managed by Coolify. Removing a managed domain offers deletion of its DNS record after confirmation; review other uses of the hostname before approving deletion.
Re-check DNS after changing a record. Coolify replaces the previous check result, including checks for preview domains. IPv6 addresses are compared by value rather than their written form.
If no zone matches, check the token's zone scope and permissions, refresh accessible zones, or configure records manually using DNS.
A proxied record that points to a different server shows DNS mismatch. See Configure Coolify DNS validation.
Use the API or MCP
You can also manage DNS records and integration tokens through the API and the MCP server:
GETandPOST /api/v1/{applications|services}/{uuid}/dns,POST .../dns/replaceandDELETE .../dns/{hostname}view, create, replace and release the Cloudflare records of a resource's domains. A release deletes the record at Cloudflare only when Coolify created it and nothing else uses it. The MCP tool ismanage_dns.PATCH /api/v1/applications/{uuid}andPATCH /api/v1/services/{uuid}create the records of the domains they add, when exactly one zone with automatic DNS manages them, like the Domains page./api/v1/security/integration-tokenslists, adds, updates, rotates and deletes integration tokens, andPOST .../{uuid}/sync-zonesreads the zones again. A new Cloudflare token can get thednsandtunnelcapabilities. The MCP tool ismanage_integration_tokens.
Use the token for SSH tunnels
To let Coolify create and manage a server SSH tunnel, also grant Account > Cloudflare Tunnel > Edit in Cloudflare and select Cloudflare Tunnel alongside DNS in the token's Coolify capabilities. DNS-only tokens cannot manage tunnels. See Server SSH tunnels for setup, DNS-conflict handling, and cleanup.
