ClouDNS Steward - manage domains & ClouDNS config
-
- Title: ClouDNS Steward - better management of domains and ClouDNS DNS configuration
- Main Page: n/a
- Git: https://git.cloudron.io/timconsidine/cloudron-cloudns-steward
- Licence: AGPL
- Dockerfile: Yes (app already packaged)
- Demo: n/a
- Install: manually or through CCAI / CCAI-P (import master catalogue to see latest additions)
- Summary: CloudDNS is a popular DNS provider. Its own portal is fully functional but limited. ClouDNS Steward wraps ClouDNS API functionality for a richer experience and extended functionality, such as scripting for bulk actions, integrity checking, domain metadata queries.
- Notes:
- I made this app for my own purposes, as I am a happy ClouDNS user but find its UI limited and a little clumsy.
- Cloudron does not directly support ClouDNS as a DNS provider. So it has to be used via the Wildcard option.
- This works totally fine, but I think the user needs to access ClouDNS portal more than they would for a supported provider.
- This app therefore "elevates" ClouDNS as a DNS provider from "unsupported" to "secondary status" (primary being supported providers).
- I don't know how many Cloudron users use ClouDNS, but there's at least 2 :laugh:. It might have niche relevancy, but that should not stop it being considered for the AppStore.
- App is protected using Cloudron proxyAuth.
- Steward uses RDAP for domain metadata (not whois.com).
- Current Functionality :
- syncs ClouDNS zones to the app library
- maintains domain metadata (expiry, registrar, tags, note)
- add, edit, delete a zone (some initial delete limitation for safety) via the app
- list all DNS records, and add, edit, delete DNS records for common (not all) record type via the app
- Roadmap :
- scripting (bulk actions across multiple domains)
- script for bulk add/update A and AAAA records for domains with a specified tag
- script for adding/updating email-related DNS records using values from Cloudron email config for a domain
- Feedback :
- any Cloudron users out there using ClouDNS : let me know any feature requests
- Alternative to / Libhunt link: e.g. n/a
- Screenshots:
-
Cool, I wonder if similar DNS management apps (Or one general one) would be useful for the primary supported DNS providers, especially those without the bulk features, etc.
-
Cool, I wonder if similar DNS management apps (Or one general one) would be useful for the primary supported DNS providers, especially those without the bulk features, etc.
-
Cool, I wonder if similar DNS management apps (Or one general one) would be useful for the primary supported DNS providers, especially those without the bulk features, etc.
@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.
Custom apps available at CCAI https://ccai.appx.uk (ask if an app is not listed in the catalogue).
-
@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.
@timconsidine you probably have with the demo server, yet limited since they're not your domains.
Happy to help as I have always used CF.
One place one might start is compliance checks for domain settings, for those with 3-10+
