DNS Manager status

import StatusPill from ‘../../../components/StatusPill.astro’;

This page summarizes DNS management behavior described in repository docs and the API state measured on 2026-11-10. It is not a full availability check: the drift report and record state were not read.

Measured state (2026-11-10)

Source: single read-only requests from the docs worktree on 2026-11-10T11:43Z.

• GET https://dns.tcp.systems/readyz returned 200 with {"providers_configured":1,"providers_total":1,"ready":true,"service":"dnsd","version":"4be1370..."}.
• GET https://dns.tcp.systems/healthz returned 200.
• GET https://dns.tcp.systems/v1/dns/zones returned 401 without a token, which matches the definition (dns, section 4: operator bearer token or a service token with aud=dns).
• The suite atlas of 2026-11-06 places the dns Nomad job on scaleblade. The dns repository’s default branch is feat/dns-cdn-slice1 (at ed847ca, 2026-11-06); which commit the live image runs is “unverified” in the atlas and was not measured here.

Earlier notes that placed dnsd on dsh are history: owner ruling 2026-11-10 removed dsh from the fleet.

Snapshot (from prior docs)

• Zones are intended to be declared in code, with drift checks.

Before DNS changes, verify the credentials and the drift state and record the date.