Skip to content

docs(sensitive): trinity as built, and DNS forwarded to AdGuard alone (#404) - #691

Merged
Gerrrt merged 1 commit into
mainfrom
gerrrt/trinity-as-built
Sep 28, 2026
Merged

Gerrrt merged 1 commit into
mainfrom
gerrrt/trinity-as-built

Conversation

@Gerrrt

@Gerrrt Gerrrt commented Sep 28, 2026

Copy link
Copy Markdown
Owner

Refs #404. It doesn't close it: step 9's timer, the DNS failure test and the step 10 gate remain.

The decision: ADR-0055, AdGuard as the only forwarder

Measured on morpheus on 2026-09-28, with the three forwarders ADR-0010 designed (AdGuard, 1.1.1.1, 8.8.8.8):

  • Forwarder RTTs: 77/201/375 ms, then 43/32/57 ms. AdGuard isn't "well under a millisecond", because an uncached lookup makes its own DoH round trip.
  • Unbound's choice isn't ordered: it picks at random among forwarders within its RTT band.
  • Leak test: of 60 random, uncacheable subdomains of a blocked domain, 38 leaked real addresses.

With AdGuard alone: 60 of 60 blocked. DNSSEC ad is still set, dnssec-failed.org still returns SERVFAIL, and the host overrides are intact.

Consequences, all written down:

The alert

  • dns.rules.yaml: AdGuardNotAnswering fires at for: 5m, severity critical. Its text says outside names are down, and gives the 1.1.1.1 workaround.
  • dns.test.yaml: asserts it's pending at 4m and firing with the new labels at 20m. promtool test rules passes.

As built

  • architecture.md: trinity is built, so check_docs now requires it in network.md and the Compute table.
  • hardware.md: the Compute row, seven Alloy agents, and the encrypted photo disk.
  • network.md:
    • trinity's row;
    • bifrost at 10.0.20.20, reserved below the pool, because it had drifted .104 → .113;
    • the Skids pass in force, with the tripwires at 0;
    • Hicks's eleventh pass (443 to trinity).
  • security.md and the firewall-claims.yaml comment.
  • ADR-0010 and ADR-0035: forward notes only.
  • The stack's README and compose.yaml headers: no longer "not built".
  • forward-dns-to-adguard.md: rewritten for a single forwarder. It now has the FreeBSD-safe leak test, and step 4 proves the page, not a fallback.
  • build-the-sensitive-tier-host.md:
    • the checkout path as used;
    • 26.04's catch-all DHCP file;
    • overlay2 set before Docker is installed;
    • bifrost's real address;
    • Home Assistant's http promotion;
    • Chrome;
    • five new failure rows.
  • Changelog entry and roadmap.

Checks

  • ./scripts/validate.sh: all checks passed, 3 skipped. The skips are the worktree-only timer-unit checks.
  • promtool test rules on dns.test.yaml: SUCCESS.

To confirm before merge

trinity's Location in network.md is written as "Shelf", which hasn't been checked against the box.

🤖 Generated with Claude Code

…#404)

Writes down the build of 2026-09-28 wherever the documents still said
"not built", and records the one decision the build forced.

ADR-0055: AdGuard is the only forwarder behind Unbound on morpheus. With
the public resolvers beside it, as ADR-0010 designed, Unbound picked among
all three within its RTT band. AdGuard is not "well under a millisecond":
a lookup it has not cached makes its own DoH round trip. 38 of 60 random
blocked subdomains leaked. With AdGuard alone, 60 of 60 were blocked, and
blocked names answer SERVFAIL, because Unbound's DNSSEC validation rejects
AdGuard's unproven DS answer. ADR-0010 and ADR-0035 gain forward notes.

Because of it, AdGuardNotAnswering is critical at 5m (it was a warning at
15m). Its text says what an outage now is, and gives the one-line
workaround. The promtool test asserts the new window and labels.

As built:
- architecture.md: trinity built.
- hardware.md: the Compute row, seven Alloy agents, and the encrypted photo
  disk.
- network.md: trinity's row, bifrost at .20 below the pool, the Skids pass
  in force, and Hicks's eleventh pass.
- security.md and the firewall-claims comment.
- The stack's README and compose.yaml headers.
- forward-dns-to-adguard.md rewritten for one forwarder: the leak test, and
  a failure test that proves the page.
- build-the-sensitive-tier-host.md: 26.04's catch-all DHCP file, overlay2
  before Docker, bifrost's real address, Home Assistant's http promotion,
  and five new failure rows.
- A changelog entry and the roadmap.

Refs #404

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Gerrrt
Gerrrt merged commit b0ad1c4 into main Sep 28, 2026
7 checks passed
@Gerrrt
Gerrrt deleted the gerrrt/trinity-as-built branch September 28, 2026 17:15
Gerrrt added a commit that referenced this pull request Sep 28, 2026
The #135 entry still read as though nothing had been done. Two of the
three acts that close it are done: morpheus forwards to AdGuard alone
since 2026-09-28 (ADR-0055, #691), and both blackbox-dns targets are
live (#690). Checked from trinity today: a blocked name through
10.0.99.1 gets no answer, and example.com is still validated (ad).

What is left is the failure test in forward-dns-to-adguard.md step 4.
It is deferred by choice, because it takes outside names from the house
for seven to ten minutes. #404's list and #135's entry now point at each
other.

Refs #135

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant