A web interface for Bindizr: manage DNS zones and records, sign and synchronize zones, and delegate access through roles.
Features · Roles and credentials · Audit log · Run with Docker · Getting Started
Work with DNS data in Zones and Records, then manage signing in DNSSEC and propagation in Secondaries. Use roles to delegate these operations and the audit log to review administrative changes. Screenshots show a running instance with example data.
Create zones, configure their SOA settings, and manage records and TTLs. Search, filter, and sort the listings, or include generated DNSSEC records when inspecting a signed zone.
Bring in a BIND zone file, a zone over AXFR, or multiple zones from a server or catalog. Validate append, upsert, or replace imports before applying them, and copy or download exports with or without DNSSEC records.
Review changes by SOA serial and author, compare record differences, and preview rollbacks. Restoring a version advances the serial for secondary synchronization.
Use the DNSSEC overview to check signed zones, then open a zone to inspect its signatures and keys. Apply reusable signing policies, manage rollovers, and copy or check the DS records published by the parent zone.
Register secondary servers, select a TSIG key for signed NOTIFY, and pause a server without removing it. Check serials and reachability, inspect AXFR/IXFR transfer history, or send NOTIFY for one or all zones, optionally advancing the serial.
Roles hold permissions; API tokens and TSIG keys act under a role. Start in Access → Roles, define what a role may do, then issue the credentials that will use those permissions.
Separate application deployments from secondary transfers with roles such as deployment and zone-transfers. The list shows each role's grant, token and key counts; a new role permits nothing until grants are added.
Open the role's Add Grant tab and choose actions for one zone or all zones. Record grants can also restrict names and types: this example allows A and AAAA records under *.apps in example.com.
Use the role's API Tokens and TSIG Keys tabs to create and review its credentials. Changing the role's grants changes what those credentials may do.
API token creation and TSIG key details
API tokens can expire; their secret is shown only when created. Creating one from a role fixes the role selection for you.
Generate or import TSIG keys for dynamic updates and zone transfers. Existing key secrets can be revealed or copied, and the key's details link back to role management.
Three logs, each under Logs in the sidebar. The audit log shows role, grant and credential changes alongside secondary and DNSSEC policy administration, filtered by entity, name or date; zone and record edits remain in the zone's version history. The access log shows every API request and nsupdate Bindizr answered, denied or failed, by caller, address and result. The transfer log shows the zone transfers each client was answered, by secondary, address, zone and result. Reading them requires log:read.
docker run -d --name bindizr-ui -p 9000:9000 kweonminsung/bindizr-ui:0.2.0-rc.1Or with Docker Compose:
docker compose up -dThen open http://localhost:9000.
Run Bindizr separately. In the setup screen, enter its URL as reachable from the UI server, provide an API token if required, and test the connection. The token's role determines the available pages and actions; an optional UI admin account protects access to this UI instance.
A v* tag, or the Manual Release workflow, builds and pushes the amd64 and
arm64 image; the Publish Image workflow pushes it under a tag you enter. To
push it from your own machine instead (the tag defaults to the version in
ui/package.json; IMAGE overrides the repository):
./scripts/build_image.shThese builds pass the selected image tag as APP_VERSION for the UI footer.
Local frontend builds use ui/package.json unless APP_VERSION is set.
Run these commands from the repository root.
-
Install dependencies and create the initial frontend build:
go mod download npm --prefix ui ci npm --prefix ui run build
-
Start Vite in one terminal:
npm --prefix ui run dev
-
Start the Go server in another terminal:
GO_ENV=development go run .
Open http://localhost:9000. The Go server forwards frontend requests to Vite on port 9001 and handles the local API and Bindizr proxy.









