Put your second nameserver in another country or data center — and manage it from a clean web panel.
Real screens of the software, shown with demo data.
If all your nameservers sit in the same data center, one outage there takes DNS down too. LionDNS lets you run a secondary nameserver on another server — for example in another European country — that keeps an up-to-date copy of every zone.
The node runs PowerDNS Authoritative and receives zones via NOTIFY/AXFR from cPanel, Plesk, BIND or PowerDNS. The web API listens locally only, and changes that need root run in a separate, constrained worker.
With an SQLite backend, set up by one installer.
cPanel DNSOnly, Plesk, BIND and PowerDNS.
Per-zone transfer signing.
Service and UDP/TCP 53 checks every 5 minutes.
Only the token’s SHA-256 hash is stored.
Backup before every upgrade and a data-preserving uninstall.
LionDNS mainly works as a secondary node that receives zones from your primary, with optional autoprimary/autosecondary provisioning.
Via an SSH tunnel or a TLS reverse proxy, since the API listens locally only.