How the local network (Thyme) works. Largely https://git.quodatum.duckdns.org/apb/thedocks
Find a file
2026-08-31 15:30:41 +01:00
omv [mod] report 2022-06-06 11:54:36 +01:00
profile.pics [init] 2022-04-17 21:56:36 +01:00
README.md Update README.md 2026-08-31 15:30:41 +01:00

DNS

evo-x2% ping google.com
ping: google.com: Temporary failure in name resolution
evo-x2% sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

evo-x2% sudo systemctl restart systemd-resolved.service

evo-x2% ping google.com
PING google.com (142.251.30.101) 56(84) bytes of data.

🥇 Option 1: Use systemd-resolved (Strongly Recommended)

This is the best practice recommended by the Tailscale documentation. systemd-resolved is Ubuntu's default DNS resolver and acts as a central manager, preventing other tools from fighting over the raw /etc/resolv.conf file.

Follow these steps to configure it:

Ensure systemd-resolved is enabled and running:

sudo systemctl enable --now systemd-resolved

Correctly symlink /etc/resolv.conf to the stub-resolv.conf file: This is critical. Tailscale expects the symlink to point to the stub file, not the main one.

sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

Restart the relevant services to apply the changes:

sudo systemctl restart systemd-resolved
sudo systemctl restart NetworkManager  # If you use NetworkManager
sudo systemctl restart tailscaled

Once this is done, the system uses systemd-resolved as the single source of truth. Tailscale and NetworkManager will no longer directly overwrite /etc/resolv.conf on their own.