First run

A new DNZ has no users. There are three ways to create the first one, a superadmin who can do everything, including managing other users, divisions and roles.

Setup page
dnz setup
Environment (Docker)

While the database is empty, every page of the dashboard redirects to /setup:

Admin account

Username, name, e-mail and password. Passwords need at least 10 characters.

First division

Every zone belongs to a division, so name the first one (for example IT). You can add the first zone here too.

Forward DNS

Pick a resolver preset (Cloudflare, Google, Quad9) or enter your own upstreams, then a forwarding strategy.

You’re signed in when it’s done.

Without the web UI, run this on the server. It asks the same questions in the terminal:

dnz setup

Or pass the answers, with the password in DNZ_PASSWORD:

DNZ_PASSWORD='…' dnz setup --username admin --division IT \
  --upstream 1.1.1.1,9.9.9.9 --zone example.com

You’re signed in to the CLI when it’s done. See CLI overview.

For automated installs, set the admin’s password in the environment. When there are no users yet, DNZ creates the admin at startup and skips the setup page.

docker-compose.yml

environment:
  DNZ_ADMIN_USERNAME: admin        # optional, default "admin"
  DNZ_ADMIN_PASSWORD: change-me-please

This admin must choose a new password at the first sign-in.

Add the people who work with DNS and give them a role in a division. See Users, divisions and roles.
Check the server’s time zone under Settings → General. Times in the UI and in notifications use it.
Set up notifications so you hear when an upstream goes down.
Point your network at DNZ. See Pointing clients at DNZ.

To start over, Settings → General → Factory reset (or dnz --reset --all) erases everything and brings the setup page back. See Settings.

Get started

Install and deploy

Dashboard

DNS

Proxy

Integrations

Administration

First run

​After the first sign-in

After the first sign-in