tailscale: Unable to resolve MagicDNS or tailnet FQDN's after macOS DNS behavior changes in OSS tailscaled 1.74.0

What is the issue?

In OSS tailscaled prior to 1.74.0 (last working version 1.72.1), I could resolve MagicDNS and tailnet FQDN’s (*.ts.net) under the following setup. The changelog notes changes in this area in 1.74.0: https://tailscale.com/changelog#2024-09-12.

  • OSS tailscaled running with --accept-dns=false
  • App Store or Standalone macOS Tailscale app running with “Use Tailscale DNS settings” off

After updating OSS tailscaled to 1.74.0, I now must turn on Tailscale DNS in the App Store or Standalone Tailscale macOS app to get MagicDNS or tailnet FQDN’s to resolve. Enabling --accept-dns on tailscaled 1.74.0 does not work to resolve MagicDNS names or tailnet FQDN’s, even with the App Store or Standalone macOS Tailscale app not running.

This is undesirable as I need to use my local network’s DNS server, with split DNS handling tailnet FQDN’s. I only turn on Tailscale DNS when using an exit node.

Please note that tailscaled runs as root (brew services start tailscale), in case that’s relevant.

Output from tailscaled 1.74.0 dns status command (with redactions):

=== 'Use Tailscale DNS' status ===

Tailscale DNS: enabled.

Tailscale is configured to handle DNS queries on this device. Run ‘tailscale set --accept-dns=false’ to revert to your system default DNS resolver.

=== MagicDNS configuration ===

This is the DNS configuration provided by the coordination server to this device.

MagicDNS: enabled tailnet-wide (suffix = REDACTED.ts.net)

Other devices in your tailnet can reach this device at REDACTED.

Resolvers (in preference order): (no resolvers configured, system default will be used: see ‘System DNS configuration’ below)

Split DNS Routes:

  • ts.net. -> 199.247.155.53
  • ts.net. -> 2620:111:8007::53

Search Domains:

  • REDACTED.ts.net

=== System DNS configuration ===

This is the DNS configuration that Tailscale believes your operating system is using. Tailscale may use this configuration if ‘Override Local DNS’ is disabled in the admin console, or if no resolvers are provided by the coordination server.

Nameservers:

  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED

Search domains:

  • home.arpa

[this is a preliminary version of this command; the output format may change in the future]

Please let me know what further info can be provided. Thank you!

Steps to reproduce

No response

Are there any recent changes that introduced the issue?

Updated OSS tailscaled (installed via brew) to 1.74.0 from 1.72.1

OS

macOS

OS version

macOS 14.6.1

Tailscale version

1.74.0

Other software

No response

Bug report

BUG-3104a4f350ae354f7eedcc95e4ce78e5b8da482124d9bbdb7feabf0f446a757f-20240913143438Z-a9cd88dd1f260627

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 5
  • Comments: 22 (1 by maintainers)

Most upvoted comments

Found another solution on macOS which is to create a domain-specific resolver file:

sudo mkdir -p /etc/resolver # if it doesn't exist already
echo "nameserver 100.100.100.100" | sudo tee /etc/resolver/ts.net
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

This should ensure that only lookups for *.ts.net are routed to tailscaled and everything else to the nameservers configured in resolv.conf.

Only minor issue I’m seeing is that host <device> doesn’t work as it only uses resolv.conf. See this note:

macOS NOTICE
       The host command does not use the host name and address resolution or the DNS query routing mechanisms used by other processes running on macOS.  The results of name or address queries
       printed by host may differ from those found by other processes that use the macOS native name and address resolution mechanisms.  The results of DNS queries may also differ from queries
       that use the macOS DNS routing library.

Instead you can use the following utility:

dns-sd -G v4 <device>

Found another solution on macOS which is to create a domain-specific resolver file:

sudo mkdir -p /etc/resolver # if it doesn’t exist already echo “nameserver 100.100.100.100” | sudo tee /etc/resolver/ts.net sudo dscacheutil -flushcache sudo killall -HUP mDNSResponder This should ensure that only lookups for *.ts.net are routed to tailscaled and everything else to the nameservers configured in resolv.conf.

This works perfectly! In my case creating the file was enough.

echo "nameserver 100.100.100.100" | sudo tee /etc/resolver/ts.net

Thanks chetan

I can confirm the same issue on tailscaled v1.76.1 from Nix on macOS 15.1. For me, manually creating a file of my domain under /etc/resolver/ fixes the issue.

I encountered a similar issue whenever I used newer tailscaled versiosn on my macs. I could not get tailnet FQDNs or shorter machine names to resolve. but they worked everywhere else on my tailnet on other devices, ubuntu installs, standalone tailscale on mac or on iphone/ipad. if I went back to v1.68.2it would start working again but I did not want to be stuck on such an old version.

what finally worked for me on my MacOS Sequoia install with v1.80.1 was to go to:

System Settings > Network > Wi-Fi (or however you connect) > Details > DNS

then add 100.100.100.100 to the DNS servers.

but also add my tailnet domain to the search domains. which finally gave me this kind of block with

scutil --dns

DNS configuration (for scoped queries)

resolver #1
  search domain[0] : MYTAILNETNAME
  nameserver[1] : 100.100.100.100
  nameserver[2] : 1.1.1.1
  nameserver[3] : 1.0.0.1
  if_index : 13 (en4)
  flags    : Scoped, Request A records
  reach    : 0x00030002 (Reachable,Local Address,Directly Reachable Address)

instead of just the not reachable search.tailscale resolver in the regular DNS configuration.

I had originally tried a lot of things from command line but ultimately only adding both via the Apple system Settings GUI ended up being what worked.

now both the tailnet FQDNs and machine names are resolving correctly in my browser as they do on any other machine in my net.