Tailscale killed my DNS

I am working on a remote location today, on a shared venue network.

After rebooting my Mac I could no longer connect to any website domain, which led me to believe that DNs was not resolving. And indeed, pinging www.google.com gave no results. Even when tethered to my iPhone, I could not connect to any website. Connecting to VPN by IP did work though, and pinging 8.8.8.8 worked fine as well.

Luckily, I could search for clues on my phone, and ran into this command that I have not used before:

scutil --dns which gives you a nice list of DNS resolvers as they are used by the system, and, on top of that list this entry:

resolver #1
  search domain[0] : tailf67a92.ts.net
  nameserver[0] : 100.100.100.100
  if_index : 24 (utun4)
  flags    : Supplemental, Request A records, Request AAAA records
  reach    : 0x00000003 (Reachable,Transient Connection)
  order    : 102000

I restarted Tailscale, and we are online again 🎉.

Comments

2 responses to “Tailscale killed my DNS”

  1. d33p.js Avatar

    @PatPitiee I had some strange issues in the past with wireguard, too. Only after rebooting, DNS resolution worked again. Never troubleshooted it, but it happens everytime, when I use wireguard.

  2. Bram Esposito Avatar

    @d33pjs I didn't investigate either, was above all happy that I solved the issue, I saw some error text in the Tailscale menu, but didn't write it down. I'll pay some more attention next time 😁

Leave a Reply