Skip to content

v1.0-rc2 — Multi-Provider DNS Registry

Pre-release
Pre-release

Choose a tag to compare

View all tags
@fuomag9 fuomag9 released this 17 Apr 16:11
· 150 commits to develop since this release
Immutable release. Only release title and notes can be modified.
v1.0-rc2
5c78a8e
This commit was signed with the committer’s verified signature.
fuomag9
SSH Key Fingerprint: VBtxaBlHKIWXUb8jfft6vrwnSToeiwPBlOO2u+pimTE
Verified
Learn about vigilant mode.

What's New

Multi-Provider DNS Registry

Replace the hardcoded Cloudflare-only DNS-01 challenge with a data-driven provider registry. Closes #37, #107.

  • 12 DNS providers supported: Cloudflare, Amazon Route 53, DigitalOcean, Duck DNS, Hetzner, Vultr, Porkbun, GoDaddy, Namecheap, OVH, Linode, IONOS
  • Configure multiple providers with encrypted credentials and select a default
  • Per-certificate provider override via the providerOptions field
  • Dynamic UI — select a provider, fill in its specific credential fields
  • Auto-migration — existing Cloudflare settings are automatically converted on upgrade
  • REST API — GET /api/v1/dns-providers for provider discovery, PUT /api/v1/settings/dns-provider to configure

Docker Images

ghcr.io/fuomag9/caddy-proxy-manager-web:v1.0-rc2
ghcr.io/fuomag9/caddy-proxy-manager-caddy:v1.0-rc2

Note: The caddy image now includes all 12 DNS provider modules. Build time is longer but all providers work out of the box.

Upgrade Notes

  • Existing Cloudflare DNS settings are automatically migrated to the new multi-provider format on startup
  • The old Cloudflare settings card in the UI is replaced by the new DNS Providers section
  • No manual action required — existing setups continue to work

Full Changelog: v1.0-RC...v1.0-rc2

Assets 3
Loading