Docker DDNS
A Docker image that uses Cloudflare DNS as a dynamic DNS provider for updating IP addresses automatically.
What is Docker DDNS?
Docker Cloudflare DDNS is a containerized tool that automatically updates Cloudflare DNS records when your public IP address changes. It solves the problem of accessing self-hosted services with dynamic IPs by providing a reliable dynamic DNS solution. The image supports multiple architectures and offers flexible configuration options.
Developers and homelab enthusiasts who self-host services behind dynamic IP addresses and use Cloudflare for DNS management. It's particularly useful for Raspberry Pi users and those running services on residential internet connections.
Developers choose this because it's a lightweight, open-source alternative to proprietary DDNS services, with native Docker support and seamless Cloudflare integration. Its multi-architecture support and extensive configuration options make it versatile for various self-hosting scenarios.
Overview
A small amd64/ARM/ARM64 Docker image that allows you to use CloudFlare as a DDNS / DynDNS Provider.
Use Cases
Best For
- Updating DNS records for self-hosted services with dynamic IPs
- Running DDNS on Raspberry Pi or ARM-based devices
- Automating Cloudflare DNS management via Docker
- Setting up IPv6 DDNS records
- Managing multiple domains through CNAME records
- Integrating DDNS into Docker Compose setups
Not Ideal For
- Users with DNS providers other than Cloudflare (e.g., AWS Route53, Google Cloud DNS)
- Environments without Docker or where containerization is not permitted
- Systems requiring advanced DNS features like load balancing, geo-routing, or DNSSEC
- Networks with strict isolation that prevent host networking for interface detection
Pros & Cons
Pros
Runs on amd64, ARM64, and ARM32 devices, including Raspberry Pi, making it versatile for various hardware setups like homelabs and embedded systems.
Allows IP pulling from specific network interfaces or custom shell commands, giving control over source detection in complex network environments.
Supports loading API keys and zone details from Docker secrets, avoiding plaintext exposure and enhancing security for production deployments.
Can delete DNS records when the container stops via DELETE_ON_STOP, preventing stale entries and simplifying management of ephemeral services.
Cons
Only integrates with Cloudflare DNS, so it cannot be used with other providers, limiting flexibility for multi-vendor or migration scenarios.
Requires Docker to run, making it unsuitable for bare-metal servers or environments where container orchestration is not available or desired.
For network interface detection, it must run with `--network host`, which bypasses container network isolation and can introduce security risks.
Frequently Asked Questions
Related Projects
cloudflaredCloudflare Tunnel client
ScrapeA Python module to bypass Cloudflare's anti-bot page.
CloudFlair🔎 Find origin servers of websites behind CloudFlare by using Internet-wide scan data from Censys.
Th3inspectorTh3Inspector 🕵️ Best Tool For Information Gathering 🔎
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.