From 1b9f78e959b7a4e7dd7ed57fec83ad523d2034ff Mon Sep 17 00:00:00 2001 From: xengineering Date: Tue, 27 Jan 2026 20:10:47 +0100 Subject: articles: arch-installation: Fix /etc/resolv.conf This was not set because it cannot be set in a chroot (see Arch Wiki about [systemd-resolved][1] section 2.1 DNS). [1]: https://wiki.archlinux.org/title/Systemd-resolved --- content/articles/arch-installation.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'content') diff --git a/content/articles/arch-installation.md b/content/articles/arch-installation.md index ae54ef3..53d776f 100644 --- a/content/articles/arch-installation.md +++ b/content/articles/arch-installation.md @@ -150,6 +150,13 @@ to describe which filesystems should be mounted where during boot. genfstab -L /mnt | tee /mnt/etc/fstab ``` +Before switching to the new system one setting regarding name resolution needs +to be done from outside. + +``` +ln -sf ../run/systemd/resolve/stub-resolv.conf /mnt/etc/resolv.conf +``` + Without actual booting a change root (`chroot`) command is used to use the new system already. @@ -176,7 +183,6 @@ DHCP=yes' > /etc/systemd/network/auto.network systemctl enable nftables.service systemctl enable systemd-networkd.service systemctl enable systemd-resolved.service -ln -sf ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf systemctl enable iwd.service systemctl enable systemd-timesyncd.service ``` -- cgit v1.2.3-70-g09d2