Skip to main content
PanelDNS manages zones and records across 22 DNS providers. Record management works everywhere. The other capabilities depend on what each provider’s own API exposes, so this page states exactly which do what.
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 notes

DNSSEC — 11 of 22

DNSSEC is not available on every provider, and on five of them it never will be — their platforms do not sign zones at all. Check this table before promising DNSSEC to a customer on a specific provider.
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:
The UI hides the DNSSEC panel wherever a provider reports it unsupported, so it is never offered and then refused.

Zone import and export

Fifteen providers use a shared BIND parser; Cloudflare, Hetzner, PowerDNS and BIND use their platform’s native import/export.
The generic export is reconstructed from PanelDNS’s own record mirror, so it does not round-trip SOA or NS records. After a generic export → import cycle, expect to re-create delegation records.
Namecheap import is lossy by design. Their setHosts 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

Namecheap exposes no API for deleting a zone — the records belong to a registered domain. Removing the zone in PanelDNS removes it locally only; it keeps resolving at Namecheap until the domain is transferred away or expires.

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.