For the technical audience
Decisions
Every architecture decision record (ADR) behind WrenDNS: what we knew, what we chose, and what it costs. This page is built from the specification on every change, so it's always the current record.
325 decisions. Accepted 115 · Agreed with the project owner. Proposed 60 · Chosen during implementation where the specification left a gap. It is in effect, and waits for the owner's review. Accepted 2026-11-18 38 · Accepted 2026-11-17 31 · Accepted 2026-11-16 16 · Accepted 2026-11-18, owner decisions 4 · Accepted 2026-11-19, T31.2 4 · Accepted 2026-11-19, T33.6, API-005, DOC-006 4 · Accepted 2026-11-17, owner decision 3 · Accepted 2026-11-19 3 · Accepted 2026-11-17, owner decision: accepted as implemented once a second independent security review found nothing HIGH or MEDIUM, which it did not 2 · Accepted 2026-11-17, owner decisions 2 · Proposed 2026-11-18 2 · Accepted 2026-11-19, owner decision 2 · Accepted 2026-11-19, T33.2 2 · Accepted 2026-11-19, amended per the owner decisions on cloud writes; owner accepted all recommendations; #41, T36.1; revised after review the same day 2 · Superseded 1 · Accepted 2026-11-18, owner decision on the precedence 1 · Accepted 2026-11-18, owner decision on the open point 1 · Accepted 2026-11-18, owner decision: any named network wins 1 · Accepted 2026-11-18, owner decision: the CA-holder residual is accepted; per-node assertion keys are T27.19 1 · Accepted 2026-11-19, owner request; revised 2026-11-18 after review for ADR-998 1 · Accepted 2026-11-19, owner request; revised 2026-11-18 after review 1 · Accepted 2026-11-18; cause unproven until real Pis confirm it 1 · Accepted 2026-11-18, T24.34 1 · Proposed 2026-11-18, T24.29 1 · Proposed 2026-11-18, T24.38 1 · Accepted 2026-11-19, owner decision; counsel review before the first commercial sale 1 · Accepted 2026-11-19, records the owner's decision 4 of docs/design/ui-technical-info.md 1 · Accepted 2026-11-19, T33.2, T33.3 1 · Accepted 2026-11-19, owner step, OPS-004 1 · Accepted 2026-11-19, T33.5 1 · Accepted 2026-11-19, T24.43, owner request 1 · Accepted 2026-11-19, owner accepted all recommendations; #41, T36.1; revised after review the same day 1 · Accepted 2026-11-19, amended per the owner decisions on cloud writes; owner accepted all recommendations; #41, #28, T36.1; revised after review the same day 1 · Accepted 2026-11-19, amended per the owner decisions on cloud writes; owner accepted all recommendations; #41, #40, T36.1; answers M32's T32.5; revised after review the same day 1 · Accepted 2026-11-19, amended per the owner decisions on cloud writes; owner accepted all recommendations; #41, T36.1; under ADR-1033, counsel review before the first sale; revised after review the same day 1 · Accepted 2026-11-19, T24.44, owner request 1 · Accepted 2026-11-19, owner decisions 1, 2 and 6; #42, T37.1 1 · Accepted 2026-11-19, owner decisions 2, 5 and 8; #42, T37.1 1 · Accepted 2026-11-19, owner decisions 7 and 10; #42, T37.1 1 · Accepted 2026-11-19, owner decisions 3, 4 and 9; #42, T37.1; amends ADR-102 for the export 1 · Accepted 2026-11-19, owner decision 2; #42, T37.1; counsel review before sale, ADR-1033 item 6 1 · Accepted 2026-11-19, amended per the owner decisions on cloud writes; #42, T37.1; under ADR-1059; owner decision D replaces the subscribed cloud lists 1 · Accepted 2026-11-19; implements owner decision B, which is final; amends ADR-054 for cloud-origin changes only; #41, T36.16, T36.17 1 · Accepted 2026-11-19; implements owner decision C, which is final; revised after the security review the same day; amends ADR-1050 points 1, 4 and 5, ADR-1051 points 1 and 6, ADR-1052 §3 and point 5, and T36.12; #41, #28, T36.12 1 · Accepted 2026-11-19, owner accepted all eight identity decisions;; owner requirement of 2026-11-19; amends ADR-1065 points 1 to 3; #41, T36.21, T36.22, T36.26 1 · Accepted 2026-11-19, owner accepted all eight identity decisions;; owner requirement of 2026-11-19; #41, T36.23 1 · Accepted 2026-11-19, owner accepted all eight identity decisions;; owner requirement of 2026-11-19; revised after the identity security review the same day; amends ADR-1049 points 1 and 2 and ADR-1061 points 3 and 5; #41, T36.24, T36.25 1 · Accepted 2026-11-19, owner accepted all eight identity decisions;; owner requirement of 2026-11-19; amends ADR-1052 point 5's Business tier; #41, T36.25, T36.27 1 · Accepted 2026-11-19, owner accepted all recommendations; owner request of 2026-11-19; M38 1 ·
<name>.localT8.3 (M8 "mDNS client naming"; API-010 lists mDNS as a naming source).or and rollup windows; pre-save checksT9.12 picks up ADR-082's "not done" (or, rollup-backed long windows) and the pre-save checks deferred from T7.5.$dnsrewrite in lists: AdGuard's precedence, a supported subsetT2.3 kept $dnsrewrite rules in the snapshot but didn't apply them (T7.20 put rewrites in the configuration).[dns] edns_payloadCode review of v0.2.0, finding 01-12 (owner's answer, 2026-10-07: a configuration key).[filter] max_regexes regex rules, 1,000 by defaultCode review of v0.2.0, finding 02-08 (owner's answer, 2026-10-07: a cap, with the overflow reported).refreshed, a cache answer; stale keeps meaning failurethe 2026-10-10 live review found a steady-state cache hit rate of about 6%: most repeat questions arrive just after their answer expired (devices cache too).public community for identity reads, by explicit per-subnet opt-inMany printers and cheap devices answer v2c public.aes 0.8 for SNMPv3 privacyThe owner asked for authPriv.[discovery]: off by default, the Home Assistant feed deferredT25.1 builds the inventory thread (wrendns-inventory) and its read-only sources.[discovery] as a managed kind: admin-only, no agent scope, and the first write waits for N−1 membersADR-907 makes [discovery] a shared section written through the config entries API as the managed kind discovery, admin-only, with dry run, If-Match and audit, and says the first write waits while any member runs N−1 (CLU-010).[discovery]ADR-907 says [discovery] node names the node that runs discovery, else the primary or the standalone node, and never an ephemeral pod or a witness.libc constantsThe m25-snmp review (2026-11-17) found two races in wrendns-snmp's credential read.offline_days 0 keeps the reservationsThe upstream merge brought T8.2's offline clients (ADR-166): the console's client history and the configured clients, named by their last address, for offline_days (30 by default, 0 for connected clients only).{n} in a quoted attribute is written as a JS expression, and a guard keeps it that wayUpstream issue #64, "2FA can't be enabled".offlineADR-942 keeps an offline UniFi client out of DNS names, discovery's bindings and a network's device count, and left /dhcp/leases without it because the API had no marker.block_in_place under the blocking helperupstream #7.[discovery] first write, and members that are stopped or run a dev buildADR-928's title says "the first write waits for N−1 members".ring, replacing openidconnect and oauth2openidconnect 4.x and oauth2 5.x pull chrono (RUSTSEC-2026-0543, unmaintained, no patched version), which deny.toml ignored (fork #17, T24.23).primary_unreachable alerts on ita replica that can't reach its primary keeps answering DNS from its last copy (CLU-004), but nothing said so: node_down only sees a node that's disconnected from the primary's view, and a replica that still reaches other members (after falling back to one of them) looks healthy while it is split off.wrendns snmp walk before the agent list exists: the lookup is the only seam, an address is refused as a name, and ownership is tested by bindingT25.4 (DSC-003, ADR-908 "Diagnostic CLI") asks for wrendns snmp walk --agent <name>, which takes a configured agent name only.[map] writes follow the settings-kinds guardthe map reads each peer's part over the cluster channel (Read::MapPart) and [map] is a shared section written through a new managed kind (ManagedKind::Map).hostname:<label> keys, a group's router_names, read off the query pathT24.9 (fork #6, API-010).identify; a group's network also takes the device firstT24.24, ADR-973's owner decision (2026-11-18): a router name ranks below the most specific CIDR and above default.RLIMIT_DATA counts what a worker holdsthe Pi-hole import worker (ADR-939) answered {"ok":false,"error":"<path>: <path>"} in every musl build, and the discovery workers (ADR-908, ADR-933, ADR-934) ran under a limit that bounded nothing.presets/categories/*.toml, sources with licence and cadence, downloaded at runtimeADR-994 needs a catalog that is data (like presets/services/*.toml, FLT-012), with sources checked for licence, maintenance and size.source is an address or a network, resolved per nodeT24.31 (UPS-013).POST /api/v1/discovery/snmp/test: a name only, a dry run, a minute between tests, run where the poller runsT25.6 asks for Test: admin, ops:discovery_test for agents, body {agent} only, dryRun lists the OIDs, Idempotency-Key, a 60 s cooldown, audited as discovery.snmp_test.[map.geoip] inside [map], a task that looks every 5 s, positional reads, an admin-only write pathT26.4 (OBS-902, NFR-001) built ADR-959.world() over merged prefixes, upstream markers while the answer address is unrecorded, a baked-in dot-grid mapT26.5 (OBS-902) built ADR-958 sections 5, 6, 8 and 9 and ADR-970's answer: the node does not record the address an answer points at, so the world view starts with the upstreams' places and says so.[map] setting, a client-side preview of the flowsT26.6 (OBS-901).client takes severalOwner request (fork #26): the Query log's client filter takes one address; the UI's list selections are a mix of checkbox lists.scripts/rebrand.py: the rename is a script, and the rule for what is historytwo branches (the CMDB and the secret-members fix) merge into feat/ipam-integrations and then main before the rename lands, and more may follow, so a hand rename would conflict on every file.permissive-final, and nothing olderADR-1033 asks for SPDX headers on new files and a check, without saying which files are new, which kinds of file count, or what is exempt.npm run check keeps the UI on-brandthe brand pass fixed what the audit found; without a check the next change can bring a hard-coded colour, a removed focus ring or an exclamation mark back.tid, generic OIDC for other IdPs, SAML through External ID until native SAML is reviewed; a portal-minted user ID as sub; verified domains, home-realm discovery, optional SSO enforcement and break-glass ownersThe owner's requirement of 2026-11-19: consumer users sign in through Entra External ID; commercial customers onboard through single sign-on as an enterprise application, federating their own IdP (Entra ID, Okta, Google Workspace and others; OIDC and SAML).No decision matches. Try fewer words, or another status or area.