The Tailscale provided DNS servers are used for all queries.when I am on a network with its own local DNS and connected to tailscale this works:.The default domain set in the Tailscale admin interface is not appended to hostname-only queries ( ping.Tailscale is not the default route (traceroute to a non-advertised route does not go through the tunnel).With version 0.98.12 on OS X we are seeing: Reach : 0x00000003 (Reachable,Transient Connection) ┆Issue is synchronized with this Asana task by Unitoįlags : Request A records, Request AAAA recordsįlags : Scoped, Request A records, Request AAAA records

It listens to the up/down of the interfaces and adds resolvers for specific domains to be used. I currently have a very specific hardcoded example that works as a work around at Tailscale version: App version: 0.95.208 I'd expect the dns set in the admin to take priority with the vpn is connected, or at least an option per client to decide nslookup with the admin dns resolves to the internal ip correctly

You'll see the public ip returned not the internal ip.

using an internal VPC dns in aws to get the internal ip vs the external ip.

ping or resolve a host where the dns would have a different ip ie.

scutil -dns should show the config in the scoped queries.

On macOS dns resolution order doesn't get prioritized with the dns in the admin panel which means it's essentially ignored.

Show dns servers mac