Skip to main content

​
Backups

With SQLite, the default, all of DNZ’s data is in one file: Take a consistent copy while DNZ runs with SQLite’s .backup:
Don’t just copy dnz.db while DNZ runs: recent changes may still be in dnz.db-wal. Use .backup, or stop DNZ first.
You can also keep zones as files: dnz zone export example.com -o example.com.zone writes a BIND zone file. See Import and export. With Postgres or MySQL, use their own tools (pg_dump, mysqldump). See Database.

​
Restoring

Stop DNZ, put the backup in place of the database file (and remove any dnz.db-wal and dnz.db-shm next to it), then start DNZ again.

​
Updates

Copy the new binary out of the new image, replace it and restart:
Database migrations run automatically at startup. Take a backup before updating, so you can go back. If you run dnz-proxy nodes, update them together with DNZ; the image ships both binaries.