F17-TS: No
Rationale
The managed service uses named control and relay infrastructure. Its fallback sends a hostname query to a bootstrap-DNS service over HTTPS; avoiding the local resolver does not eliminate name resolution from the selected stack.
Assessment method
Primary documentation, pinned source and explicit whole-stack inference
Source context
Tailscale bootstrap DNS, infrastructure requirements and RFC 4271
Outstanding qualification
MagicDNS may be optional for peer traffic. This verdict concerns the complete managed lifecycle, not whether an already connected peer can be addressed numerically.
Public sources
- https://raw.githubusercontent.com/tailscale/tailscale/566f89e0fb2aa4b2f1ebf98761e45e62aa5ef225/net/dnsfallback/dnsfallback.go
- https://raw.githubusercontent.com/tailscale/tailscale/566f89e0fb2aa4b2f1ebf98761e45e62aa5ef225/net/dnsfallback/dnsfallback.go
- https://tailscale.com/docs/reference/faq/firewall-ports
- https://www.rfc-editor.org/rfc/rfc4271.html#section-3.2
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round590.html
- round590-sources.json