@robi at your suggestion, I checked about DNS providers offering an API.
Cloudron supported DNS providers :
- AWS Route 53 – Yes, full REST/Query API and SDKs.
- Bunny (Bunny.net DNS) – Yes, HTTP API for DNS zones/records.
- Cloudflare – Yes, very complete REST API.
- deSEC – Yes, JSON API (desec.io).
- DigitalOcean – Yes, v2 API for DNS.
- DNSimple – Yes, full REST API.
- Gandi LiveDNS – Yes, HTTP API for LiveDNS.
- GoDaddy – Yes, REST API for DNS and domain management.
- Google Cloud DNS – Yes, Google Cloud API (REST + client libraries).
- Hetzner (Robot / DNS) – Yes, DNS API via Robot; plus…
- Hetzner Cloud – Yes, separate Cloud API (mainly servers, networks, but supports reverse DNS).
- INWX – Yes, DNS API (REST and XML‑RPC style).
- Linode – Yes, v4 API with DNS endpoints.
- Name[.]com – Yes, REST API including DNS.
- Namecheap – Yes, XML‑based HTTP API with DNS functions.
- Netcup – Yes, DNS API (JSON over HTTPS).
- OVH – Yes, OVHcloud API includes DNS.
- Porkbun – Yes, JSON HTTP API for DNS and domains.
- Vultr – Yes, v2 API for DNS.
Other well‑known DNS providers with APIs :
- Azure DNS (Microsoft Azure)
- NS1 (nsone)
- CloudNS
- Dyn Managed DNS (now Oracle Cloud Infrastructure DNS)
- PowerDNS (via its own API, if you self‑host)
- Huawei Cloud DNS, Alibaba Cloud DNS, etc.
So if there is demand, there is certainly scope for making Steward support those, as separate apps or some multi-provider app.
I'm going to get ClouDNS Steward to a point I am happy with and then review this.
As I have never used a Cloudron-supported dns provider, I don't yet know what benefit users would have via Steward. But I can look into that later.