CloudFlare DDNS

This small image will allow you to use the free CloudFlare DNS Service as a Dynamic DNS Provider (DDNS).

Created 3 years ago - Last update 3 years ago

This small Alpine Linux based Docker image will allow you to use the free CloudFlare DNS Service as a Dynamic DNS Provider (DDNS). Default values are tuned to work with CapRover. To create a CloudFlare API token for your DNS zone go to https://dash.cloudflare.com/profile/api-tokens and follow these steps: 1 - Click Create Token 2 - Provide the token a name, for example, cloudflare-ddns 3 - Grant the token the following permissions: Zone - Zone Settings - Read Zone - Zone - Read Zone - DNS - Edit 4 - Set the zone resources to: Include - All zones 5 - Complete the wizard and copy the generated token into the Cloudflare API token field

Deployed services

cloudflareddns

oznu/cloudflare-ddns:latest

Variables

Cloudflare API token

Default:

$$cap_api_key
Your CloudFlare scoped API token. See the Creating a Cloudflare API token upward.

DNS zone

Default: captain.yourdomain.com

$$cap_zone
The DNS zone that DDNS updates should be applied to. Defaults to your CapRover root domain.

Zone's subdomain

Default: *

$$cap_subdomain
A subdomain of the ZONE to write DNS changes to. If this is not supplied the root zone will be used. Defaults to your CapRover apps subdomains.

Proxied?

Default: false

$$cap_proxied
If you are using free ClourFlare tier, leave as false. Set to true to make traffic go through the CloudFlare CDN.

Resource record type

Default: A

$$cap_rrtype
Set to AAAA to use set IPv6 records instead of IPv4 records. Defaults to A for IPv4 records.

DNS server

Default: 1.1.1.1

$$cap_dns_server
Set to the IP address of the DNS server you would like to use. Defaults to 1.1.1.1 (CloudFlare DNS) otherwise.

Cron

Default: */5 * * * *

$$cap_cron
Sets how often your container checks for IP changes. Defaults to every 5 minutes. You can read more about CRON configuration here https://en.wikipedia.org/wiki/Cron