Open the server Apps tab
Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.


Dynamic DNS client that keeps a Cloudflare DNS record pointed at the host's current public IP
Add your server credentials to Server Compass
Choose from our template library
Fill in settings and click Deploy
Use the Cloudflare DDNS template in Server Compass to deploy a maintained DDNS Updater dashboard, then add Cloudflare DNS credentials after the service is running.
Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.

Click New App and choose the template deployment path so Server Compass can load the built-in catalog.

Use the template picker search to find Cloudflare DDNS in the Server Compass template catalog.

Choose the Cloudflare DDNS template. Server Compass fills the DDNS Updater service, dashboard port, persistent data volume, and conservative polling settings.

Confirm the app name and service settings. In this run, the app was named cloudflare-ddns-demo; the dashboard was exposed on host port 4142.

Review the generated compose settings, confirm the DDNS Updater image, dashboard port, and data volume, then click Deploy.

Keep the deployment modal open while Server Compass uploads the compose file, pulls the DDNS Updater image, starts the container, and verifies the stack.

After deployment finishes, return to the Apps tab and confirm the Cloudflare DDNS app is marked Running.

Open the public dashboard URL and confirm the DDNS Updater table loads. The empty table is expected until you add a Cloudflare setting and token after deployment.

The DDNS Updater dashboard loaded successfully in Chromium at http://91.99.15.247:4142/.
It deploys qmcgaw/ddns-updater with a persistent data volume and web dashboard. Cloudflare records are not changed until you add a scoped Cloudflare token and DNS setting.
The tutorial used host port 4142, mapped to the DDNS Updater dashboard on container port 8000.
No. The tutorial verifies the service and dashboard without sending a DNS update. Add your own scoped Cloudflare token after deployment to enable real updates.
No. The deployment guide should live on the Cloudflare DDNS template detail page and be linked from the reusable template deployment docs page.
After deploying Cloudflare DDNS with Server Compass, complete these steps to finish setup
Verify in Cloudflare's DNS dashboard that the record `{{SUBDOMAIN}}.{{ZONE}}` was updated to your current public IP
Watch `docker logs <container>` for any auth errors
Add additional DDNS containers for extra subdomains if needed
Need help? Check out our documentation for detailed guides.
Common questions about self-hosting Cloudflare DDNS
Simply download Server Compass, connect to your VPS, and select Cloudflare DDNS from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.
Cloudflare DDNS requires a minimum of 64MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.
Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard Cloudflare DDNS backup and restore procedures.
Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest Cloudflare DDNS image will be pulled and deployed with zero downtime.
Cloudflare DDNS is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.
Download Server Compass and deploy Cloudflare DDNS to your VPS in under 3 minutes. No Docker expertise required.
Download Server Compass