mailu: every container asks the module's own resolver, pinned where they can find it #78

2026-09-25T21:49:26Z

jschoubben commented

2026-09-25 21:49:26 +00:00

Found live in the Phase-2 window: 2024.06's admin refuses to serve behind a non-DNSSEC-validating resolver (unhealthy admin → 454 on submission → 500 webmail). The unbound this module always shipped becomes reachable: pinned at the predecessor's own address (192.168.203.254, on the subnet the mesh adopted) via the new ip field, and named as dns by the nine containers that resolve anything. Stands on mesh-host #26.

Found live in the Phase-2 window: 2024.06's admin refuses to serve behind a non-DNSSEC-validating resolver (unhealthy admin → 454 on submission → 500 webmail). The unbound this module always shipped becomes reachable: pinned at the predecessor's own address (`192.168.203.254`, on the subnet the mesh adopted) via the new `ip` field, and named as `dns` by the nine containers that resolve anything. Stands on mesh-host #26.

jschoubben added 1 commit 2026-09-25 21:49:26 +00:00

mailu: every container asks the module's own resolver, pinned where they can find it 047f228fe3

2024.06's admin refuses to serve behind a resolver that does not
validate DNSSEC — found live as an unhealthy admin, 454s on submission
and a 500 webmail, with the runtime's forwarder validating nothing. The
unbound this module always shipped becomes reachable: pinned at the
predecessor's own address on the module network (the subnet the mesh
adopted), and named as dns by the nine containers that resolve anything.
Stands on mesh-host #26, which gave the vocabulary these two fields.

jschoubben merged commit 7cb7659fbe into main

2026-09-25 21:49:31 +00:00

jschoubben deleted branch feat/mailu-points-at-its-own-resolver

2026-09-25 21:49:31 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#78