Repository navigation
docs(sensitive): trinity as built, and DNS forwarded to AdGuard alone (#404) - #691
Merged
Merged
Conversation
…#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>
This was referenced Sep 28, 2026
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>
14 of 27 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
morpheuson 2026-09-28, with the three forwarders ADR-0010 designed (AdGuard,1.1.1.1,8.8.8.8):With AdGuard alone: 60 of 60 blocked. DNSSEC
adis still set,dnssec-failed.orgstill returnsSERVFAIL, and the host overrides are intact.Consequences, all written down:
SERVFAIL, because Unbound validates and AdGuard's DS answer for a blocked zone carries no proof.trinityis the house's DNS dependency.AdGuardNotAnsweringis now critical at 5m (it was a warning at 15m).The alert
dns.rules.yaml:AdGuardNotAnsweringfires atfor: 5m, severitycritical. Its text says outside names are down, and gives the1.1.1.1workaround.dns.test.yaml: asserts it's pending at 4m and firing with the new labels at 20m.promtool test rulespasses.As built
architecture.md:trinityis built, so check_docs now requires it innetwork.mdand the Compute table.hardware.md: the Compute row, seven Alloy agents, and the encrypted photo disk.network.md:trinity's row;bifrostat10.0.20.20, reserved below the pool, because it had drifted.104→.113;trinity).security.mdand thefirewall-claims.yamlcomment.compose.yamlheaders: 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:overlay2set before Docker is installed;bifrost's real address;httppromotion;Checks
./scripts/validate.sh: all checks passed, 3 skipped. The skips are the worktree-only timer-unit checks.promtool test rulesondns.test.yaml: SUCCESS.To confirm before merge
trinity's Location innetwork.mdis written as "Shelf", which hasn't been checked against the box.🤖 Generated with Claude Code