User ManualPodWarden
Settings: DDNS
Dynamic DNS configurations for automatic IP address updates
What you see
URL: /settings (DDNS tab)
The DDNS tab manages Dynamic DNS configurations. Each configuration maps a domain to a DDNS provider so that PodWarden can automatically update DNS records when your public IP address changes. This is essential for homelab and self-hosted setups without static IP addresses.
Fields / columns
| Column | Description |
|---|---|
| Provider | The DDNS service provider (e.g. cloudflare, duckdns, podwarden-hub) |
| Domain | The domain or subdomain to update (e.g. home.example.com) |
| Token | API token or credentials for the DDNS provider (displayed masked) |
| Update interval | How often PodWarden checks and updates the IP address (e.g. 5m, 15m, 1h) |
| IP source | How PodWarden detects the current public IP (auto, web, or a specific interface) |
Available actions
| Action | Where | What it does |
|---|---|---|
| Create | List page toolbar | Opens the DDNS configuration form |
| Edit | Config row | Modify the provider, domain, token, interval, or IP source |
| Delete | Config row | Removes the DDNS configuration and stops automatic updates |
| Test | Config row | Performs an immediate IP detection and attempts a DNS update. Reports the detected IP and whether the update succeeded |
Status badges
| Badge | Meaning |
|---|---|
| active | DDNS updates are running on schedule |
| ok | Last update succeeded |
| failed | Last update attempt failed (check the error message) |
| disabled | Configuration exists but updates are paused |
Supported providers
PodWarden supports several DDNS providers out of the box. The podwarden-hub provider uses Hub DDNS subdomains allocated from the Hub DDNS service.
Related docs
- Ingress and DDNS guide -- Detailed DDNS setup walkthrough
- Hub DDNS -- Allocate subdomains from PodWarden Hub
- Ingress -- Ingress rules that use DDNS-managed domains
- Settings -- Hub -- Previous settings tab
- Settings -- MCP -- Next settings tab