This matrix is generated from each driver’s
capabilities() method, and a CI guard
fails the build if a flag disagrees with the code. It is what the application
actually believes, not a summary written alongside it.Matrix
Legend — ✅ supported · ❌ not supported · ⚠️ conditional, see notesDNSSEC — 11 of 22
Not possible (5). DigitalOcean has no DNSSEC; Linode and Hetzner do not sign zones; DNS Made Easy does not expose it in its public API; Namecheap’s DNS API has no DNSSEC operation. These return a specific “not supported by this platform” error rather than a generic one. Not yet built (6). Each is blocked on something concrete:Why the remaining six are not implemented
Why the remaining six are not implemented
Zone import and export
Fifteen providers use a shared BIND parser; Cloudflare, Hetzner, PowerDNS and BIND use their platform’s native import/export. Namecheap import is lossy by design. TheirsetHosts API accepts only
A, AAAA, CNAME, MX, MXE, TXT, URL, URL301 and FRAME — so SRV, CAA, NS and PTR records
in a BIND file are skipped. It is flagged as supported because it genuinely works for
everything else.
Zone deletion on Namecheap
A note on the ⚠️ in the rDNS and Secondary columns
Those flags are set on the driver but nothing in the application reads them yet —dnssec is currently the only capability the UI acts on. Treat rDNS and Secondary as
informational until they are wired up.