Support Domain Chief
-
Please add https://domain.chief.app to the list of supported DNS providers.
This guy seems to do everything right:
European-based, DNSSEC, free WHOIS privacy, free SSL, transparent pricing, API, MCP, e-mail forwarding, etc. -
Interesting other suite of apps too: https://chief.app/
-
Small update on this one: instead of only asking, here is the provider. Zip: https://drive.proton.me/urls/Y38WADGTY4#XXti7YPFmh3I
Domain Chief DNS backend for Cloudron, built against
master@712e9e2. Both patches apply cleanly withgit am.What's in the zip:
0001-dns-add-Domain-Chief-DNS-provider.patch:src/dns/domainchief.js(the seven-method DNS interface), registration insrc/dns.jsandsrc/domains.js, the provider entry plus token/team fields in the dashboard, and 9 mocked tests insrc/test/dns-providers-test.js0002-domains-document-Domain-Chief-DNS-provider.patch: thedocs/domains.mdsectionMR-DESCRIPTION.md: design notes, what I tested, what I could not testfiles/domainchief.js: the new provider on its own, if you want to read it without applying anything
The parts that needed thought:
ctp_personal tokens are not team-scoped, so the config has an optional team that is sent asX-Chief-Team.ctt_team tokens do not need it.- The API requires a TTL and Cloudron's interface does not pass one, so records are created with 300s. That matters because
wait()polls the authoritative nameservers before a certificate is issued. - The record listing is paginated at 100 per page, so the provider walks all pages before filtering by name and type. Reading only the first page would make deletes miss records and upserts duplicate them - the quickest way to eat someone's MX records.
verifyDomainConfig()checks that the domain exists in the team, thatis_using_hosted_dnsis true and that the NS delegation points at Domain Chief, then writes and removes acloudrontestdnsrecord to prove the token may write.
Verified so far: the nock tests (create, update in place, prune leftovers, two-page listing, apex matching, value-scoped delete, MX priority mapping), eslint clean on every changed file, and both patches apply to a fresh clone of master.
Not verified: Domain Chief has no sandbox mode, so I could not run it against the real API. The free
.exampleTLD covers record CRUD; one end-to-end run (DNS-01 with Let's Encrypt staging) needs a real domain. Happy to do both, or to hand over a token for a throwaway team, if that helps review.Still missing and better done upstream: three translation keys (
domains.domainDialog.domainChiefToken,domainChiefTeam,domainChiefTeamPlaceholder- I did not touch the Weblate files), a screenshot for the docs section, and confirmation that the API accepts*as a record name before wildcard TLS is advertised as supported.If a merge request is easier than a zip, tell me.
-
Hi All,
I was notified of this thread and great to see there is interest in bringing Domain Chief DNS to Cloudron.
I am not familiar with Cloudron at the moment but if there are any questions or I can provide guidance please let me know and I'll see what I can do to help out!
Greetings from Alex @ Domain Chief
-
-
Hi All,
I was notified of this thread and great to see there is interest in bringing Domain Chief DNS to Cloudron.
I am not familiar with Cloudron at the moment but if there are any questions or I can provide guidance please let me know and I'll see what I can do to help out!
Greetings from Alex @ Domain Chief
@stayallive Great that you joined. Now I csn bug you here, too.

Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login