If a new DNS Provider has been added, you have to remove and reinstall caddy to get the latest binary. Just updating is not enough. Don't worry, your configuration won't be deleted.
DNS Providers that use the standard "dns provider apikey" in the Caddyfile
[x] - Cloudflare is already implemented in Version 1.1.4r
[x] - duckdns - Yes
[x] - digitalocean - Yes
[x] - dnspod - Yes
[x] - hetzner - Yes
[x] - godaddy - Yes
[x] - gandi - Yes
[x] - vultr - Yes
[x] - ionos - Yes (not that popular but I need this)
DNS Providers who need bells and whistles:
route53 - Needs too many custom fields. Only if there's high demand.
alidns - Needs too many custom fields. Only if there's high demand.
googleclouddns - Needs too many custom fields. Only if there's high demand.
azure - Needs too many custom fields. Only if there's high demand.
Current build:
If a new DNS Provider has been added, you have to remove and reinstall caddy to get the latest binary. Just updating is not enough. Don't worry, your configuration won't be deleted.
DNS Providers that use the standard "dns provider apikey" in the Caddyfile
DNS Providers who need bells and whistles:
route53 - Needs too many custom fields. Only if there's high demand. alidns - Needs too many custom fields. Only if there's high demand. googleclouddns - Needs too many custom fields. Only if there's high demand. azure - Needs too many custom fields. Only if there's high demand.