Skip to content

Conversation

samuelpecher
Copy link
Contributor

On first run, symlink systemd-resolved's resolver into /etc/resolv.conf

  • use first-run script due to chroot restrictions
  • add to password-less sudo first-run commands

Matches migration 1754984623

dhh and others added 2 commits October 1, 2025 23:27
On first run, symlink systemd-resolved's resolver into /etc/resolv.conf

Matches migration 1754984623
@samuelpecher samuelpecher self-assigned this Oct 2, 2025
@dhh
Copy link
Member

dhh commented Oct 5, 2025

What is this fixing or adding?

@samuelpecher
Copy link
Contributor Author

New installs weren't picking up proper DNS settings as /etc/resolv.conf didn't point to the stub resolver config created by systemd-resolved. This fixes that, in line with Arch's docs instruction to enable to symlink.

This was enabled in #812, and taken out in preparation for #752, but without the symlink the new settings won't be picked up on a fresh install.

@flavorjones
Copy link
Member

👍 I needed to make this change manually this morning after an Omarchy upgrade before Tailscale DNS would work for me.

@dhh
Copy link
Member

dhh commented Oct 6, 2025

Great. We probably need a migration to fix this for existing installations too, yeah?

@dhh
Copy link
Member

dhh commented Oct 7, 2025

Will merge this for now. Please do a follow-up PR with the migration we need.

@dhh dhh changed the base branch from master to dev October 7, 2025 12:26
@dhh dhh merged commit e6d1a2f into dev Oct 7, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants