// troubleshooting guide · tailscale
Tailscale MagicDNS Not Working
- Status
- Workaround available
- platforms:
- Linux, Android, Windows, macOS
- updated:
- November 16, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · tailscale/magicdns-not-working4 FIXES
// quick answer
MagicDNS breaks most often on Linux, where Tailscale and NetworkManager or another resolver fight over /etc/resolv.conf. Use systemd-resolved, or run 'tailscale set --accept-dns=false' on hosts with their own DNS such as Pi-hole.
Most likely fix: Check DNS outside Tailscale first
How to fix it
// try these in order, the most common fix is first
FIX 1Check DNS outside Tailscale first
- 01Disconnect Tailscale and test name resolution
- 02If it works without Tailscale, Tailscale's DNS settings are involved
Did this fix it?FIX 2Use systemd-resolved on Linux
- 01Run 'resolvectl status' and check whether /etc/resolv.conf is a symlink to the systemd stub
- 02If using NetworkManager, set dns=systemd-resolved in its config
- 03Relink /etc/resolv.conf to /run/systemd/resolve/stub-resolv.conf and restart NetworkManager, systemd-resolved and tailscaled
Did this fix it?FIX 3Stop Tailscale managing DNS on that host
- 01Run 'sudo tailscale set --accept-dns=false'
- 02MagicDNS at 100.100.100.100 still answers if you query it directly
Did this fix it?FIX 4Check the tailnet DNS settings
- 01Open the DNS page in the admin console and verify nameservers and MagicDNS are enabled
- 02Make sure the policy allows devices to reach the configured nameservers
Did this fix it?
SANDBOX · tailscale RUNS IN YOUR BROWSER
Try it: connect to a server and see what websites see
A hands-on Tailscale-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
Device names or .ts.net hostnames don't resolve, all DNS stops working after 'tailscale up', or /etc/resolv.conf keeps getting overwritten.
Why it happens
- C-01No DNS manager running, so Tailscale rewrites /etc/resolv.conf
- C-02NetworkManager writing resolv.conf directly instead of through systemd-resolved
- C-03Pi-hole or a custom resolver on the same host
- C-04Nameservers in the Tailscale DNS settings blocked by the access policy
- C-05Corporate or ISP DNS rebinding protection blocking private IPs
// this guide also covers
- tailscale magicdns not working
- tailscale dns not working
- tailscale overwriting resolv.conf
- tailscale accept-dns
Still not working?
If Tailscale keeps failing, you're not alone. See every Tailscale problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to us