https://pawal.codeberg.page/gonemaster/index.htmlStart with the path that matches what you are doing. The older top-level pages remain in place while the documentation is being split into narrower guides. Common Paths I want to… Start here Run one DNS check locally cli/ Start and operate the HTTP server server/ Automate the server from a shell or script client/ Manage domain tags and batch runs analysis/tags.md Publish public cohort analysis analysis/ Integrate with Nagios or Icinga nagios.md Call the engine from Go dev.md Server server/README.md : server overview, API boundaries, job lifecycle. server/configuration.md : flags, environment variables, config files, profiles. server/database.md : storage backends, DSNs, retention, backups. server/operations.md : jobs, batches, queue controls, purge, deletion, health. server/public-api-and-proxy.md : public endpoints, rate limiting, reverse proxies. server/performance.md : worker sizing, hot-cache, resolver tuning. server/ui.md : embedded admin UI, public UI, analysis UI. Client client/README.md : gonemaster-client overview. client/jobs.md : submit, watch, cancel, purge, and fetch job results. client/batches.md : run many domains and manage batch results. client/domains-tags-runs-entries.md : query stored analysis data. client/examples.md : common command sequences. Direct local tests with the gonemaster binary stay in cli/ .Hugoen-ushttps://pawal.codeberg.page/gonemaster/cli/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://pawal.codeberg.page/gonemaster/cli/index.htmlThis page documents gonemaster, the direct local test runner. It runs the engine in the current process without gonemaster-server. gonemaster normalizes IDN domains to IDNA A-labels before use. This page is for the local runner only. The server client is documented under client/ , including job and batch operations. Installation Install the CLI with Go: go install codeberg.org/pawal/gonemaster/cmd/gonemaster@latest For local development from a checkout: go build -o gonemaster ./cmd/gonemaster Synopsis gonemaster [flags] [DOMAIN] Notes:https://pawal.codeberg.page/gonemaster/server/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://pawal.codeberg.page/gonemaster/server/index.htmlgonemaster-server runs DNS tests through an HTTP API, stores results, and serves the admin and public web interfaces. Surfaces Path Audience Purpose / Trusted operators Admin UI for jobs, batches, domains, tags, cohorts, and settings. /api/v1/ Trusted clients Full admin API used by the admin UI, gonemaster-client, and scripts. /public/ Public users Single-domain public test UI. /analysis/ Public users Read-only public cohort analysis UI. /pub/api/v1/ Public clients Restricted API for public jobs, public profiles, and analysis views. Do not expose / or /api/v1/ directly to untrusted clients. The public surfaces are designed for internet exposure when rate limiting and reverse proxy rules are configured.https://pawal.codeberg.page/gonemaster/client/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://pawal.codeberg.page/gonemaster/client/index.htmlgonemaster-client is the command-line client for gonemaster-server. Use it when you want to submit jobs, run batches, inspect stored results, or query tagged analysis data through the admin API. For direct local tests that do not use the server, use ../cli/ . Connection The default server is: gonemaster-client --server http://localhost:8080/api/v1 jobs list Set --server to the admin API base URL. Public API endpoints are not the default target for this client.https://pawal.codeberg.page/gonemaster/analysis/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://pawal.codeberg.page/gonemaster/analysis/index.htmlGonemaster can run large domain sets, store historical results, and publish read-only cohort views for public analysis. Concepts A tag is a named collection of domains. A batch runs tests for many domains, often selected from a tag. A cohort is a curated public dataset backed by one source tag. A snapshot is an immutable view of a cohort captured from one snapshot-intent batch. Workflow Create a tag and add domains. Run a tagged batch. Create or enable a cohort for the tag. Capture a snapshot. Share the public analysis URL. Guides Tags: tags.md Cohorts: cohorts.md Snapshots: snapshots.md Querying: querying.md Public UI: public-ui.mdhttps://pawal.codeberg.page/gonemaster/specifications/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://pawal.codeberg.page/gonemaster/specifications/index.htmlThis directory contains the canonical testcase specifications for gonemaster. The Zonemaster project may be used as an upstream reference during migration, but the documents in this tree define and describe gonemaster behavior. Goals Document each implemented gonemaster testcase with exact behavior. Treat emitted tags as part of the testcase contract. Keep documentation aligned with code through explicit workflow and validation. Documents Testcase Specifications tests/ - Canonical per-testcase specifications (algorithm, emitted tags, arguments, severity, upstream differences). tags/ - Per-module tag catalogs with severity levels and i18n coverage. Inventories implemented-testcases.md - Authoritative list of all implemented testcases. possible-tags-by-testcase.md - All possible tags per testcase, derived from code metadata. log-args-inventory.md - Current inventory of emitted log argument keys, tags, value shapes, and producer file paths. Gap and Divergence Tracking known-intentional-gaps.md - Upstream testcase gaps that are intentionally not implemented, with rationale. known-behavior-divergences.md - Behavior divergences identified during investigation, tagged for review. Migration upstream-testcase-matrix.md - Maps upstream Zonemaster specs to gonemaster testcase IDs and migration status. Reference templates/ - Reusable templates for testcase specs and tag tables. log-args-coherency.md - Shared glossary and invariants for log argument naming/types. log-args-key-glossary.md - Canonical v1.1 key/type glossary for machine consumers. Source-Of-Truth Rules Gonemaster implementation is the runtime source of truth. docs/specifications/tests/ is the documentation source of truth for expected behavior. docs/specifications/upstream/ is reference-only and can differ from gonemaster. Any intentional divergence from upstream must be documented in the gonemaster testcase spec. Outside the plans directory tree, gonemaster docs must not reference files in plans. Update Workflow Identify testcase behavior from current gonemaster code. Compare with upstream reference when relevant. Write or update canonical spec in tests/ using the testcase template. Update tag documentation in tags/ using the tag table template. Add follow-up issues for unresolved ambiguities. Tooling Refresh generated inventories:https://pawal.codeberg.page/gonemaster/man/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://pawal.codeberg.page/gonemaster/man/index.htmlThese are the gonemaster man pages in rendered form. The canonical format is the compiled man page installed with the binary.