novox/mesh-catalog
3
0
Fork 0
Code Issues Pull Requests 19 Packages Projects Releases Wiki Activity

mailu: admin asks the machine's resolver, not Mailu's own #178

Merged
jschoubben merged 1 commits from fix/mailu-admin-asks-the-machines-resolver into main 2026-09-30 13:13:29 +00:00
Conversation 0 Commits 1 Files Changed 1
+2 -5
jschoubben commented 2026-09-30 13:13:26 +00:00
Owner
Copy Link
Copy Source

Since the mesh stopped copying names into containers (ADR 0148), mailu-admin could not resolve its database host through Mailu's unbound. It now uses the machine's resolver like every container without a dns of its own.

Since the mesh stopped copying names into containers (ADR 0148), mailu-admin could not resolve its database host through Mailu's unbound. It now uses the machine's resolver like every container without a dns of its own.
jschoubben added 1 commit 2026-09-30 13:13:27 +00:00
mailu: admin asks the machine's resolver, not Mailu's own 47f6e7d78b 
admin is the one container here that reaches something by a mesh name:
the database, bound in database.env. A mesh name is answered by the
machine's resolver, which the runtime hands every container that does
not name its own (novox/hq ADR 0148); Mailu's unbound knows no mesh
name, and since the mesh stopped copying names into containers admin
could not find its database. The others keep unbound — rspamd needs a
validating resolver for DNSBL lookups and asks for no mesh name.
jschoubben merged commit 4449f44cf1 into main 2026-09-30 13:13:29 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jschoubben miel.truyen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#178