systemd-resolved: a machine's own resolver, routing a VPN's domains by link (hq ADR 0247) #113

Merged
mesh-admin merged 2 commits from feat/systemd-resolved-split-dns into main 2026-10-07 20:14:22 +00:00
Showing only changes of commit 60641176ab - Show all commits
+2 -1
View File
@@ -71,7 +71,8 @@ same three, plus:
- `route` with `takes` (the write's `id`) and `by` (the module's name): route, then take that write, so
the module's file is put back.
A VPN's servers and domains go over this socket and never over the bus, so they never leave the machine.
A VPN's servers and domains are handed over on this socket, never over the bus. They cross the bus only
as the answer to `routes` when the operator asks it, and nothing keeps that answer.
resolved holds the routes itself, per link, and forgets a link's route when the link goes. Nothing here
keeps a table of its own that could disagree with it.