Add global DNS search domain to fix NFS mounts on lxc-docker #23

Merged

beatzaplenty merged 1 commits from worktree-fix-container-dns-search-domain into main

2026-07-21 00:11:23 +00:00

Author	SHA1	Message	Date
beatzaplentyandClaude Sonnet 5	e176ff723d	Add global DNS search domain to fix NFS mounts on lxc-docker Check NixOS configurations / eval-hosts (pull_request) Failing after 40m2s Details Cross-host references throughout this repo (vars.nfsServerHost, vars.nixCacheHost, vars.dockerHost) are bare short names, not FQDNs. Resolving them has always depended on whatever network stack happens to be in play picking up the DHCP-advertised domain as a search suffix -- NetworkManager does this by default, which is why it went unnoticed everywhere else, but LXC containers force-disable NetworkManager and get their systemd-networkd config written directly by Proxmox instead, which never sets one. Confirmed live on lxc-docker (vmid 105) after today's earlier fix for the automount/mount=nfs bugs: systemd-resolved had no search domain for eth0, so "server" failed to resolve ("Name or service not known") while "server.sweet.home" resolved fine via the same DNS server -- every NFS mount in modules/docker/mount-data.nix was still failing. networking.search sets systemd-resolved's own Domains= globally rather than depending on the per-link DHCP path, so it isn't at the mercy of whichever component owns a given host's interface file. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T48qgH3VTvs8wvwj44FEbE	2026-07-20 18:22:12 +00:00

Author

SHA1

Message

Date

beatzaplentyandClaude Sonnet 5

e176ff723d

Add global DNS search domain to fix NFS mounts on lxc-docker

Check NixOS configurations / eval-hosts (pull_request) Failing after 40m2s

Details

Cross-host references throughout this repo (vars.nfsServerHost,
vars.nixCacheHost, vars.dockerHost) are bare short names, not FQDNs.
Resolving them has always depended on whatever network stack happens
to be in play picking up the DHCP-advertised domain as a search
suffix -- NetworkManager does this by default, which is why it went
unnoticed everywhere else, but LXC containers force-disable
NetworkManager and get their systemd-networkd config written directly
by Proxmox instead, which never sets one.

Confirmed live on lxc-docker (vmid 105) after today's earlier fix for
the automount/mount=nfs bugs: systemd-resolved had no search domain
for eth0, so "server" failed to resolve ("Name or service not known")
while "server.sweet.home" resolved fine via the same DNS server --
every NFS mount in modules/docker/mount-data.nix was still failing.

networking.search sets systemd-resolved's own Domains= globally
rather than depending on the per-link DHCP path, so it isn't at the
mercy of whichever component owns a given host's interface file.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T48qgH3VTvs8wvwj44FEbE

2026-07-20 18:22:12 +00:00