C05-TS: No
Rationale
The selected fresh user-enrollment flow requires the managed login page and an external identity provider in a web browser. With external DNS unavailable and no name cache or pre-provisioned authentication key, that browser cannot resolve the required service names. The daemon-specific bootstrap resolver does not provision name resolution for the browser and identity-provider flow. The complete selected bootstrap therefore does not meet C05.
Assessment method
Primary enrollment documentation and scoped bootstrap dependency analysis; no runtime test
Source context
Tailscale identity, Linux installation and auth-key documentation
Outstanding qualification
Documentary dependency inference, not an executed outage test. This is initial interactive user enrollment, not already enrolled nodes reconnecting. Pre-provisioned auth keys can bypass browser login and constitute a different initial state; they are not assumed here. Tailscale has a numeric-address HTTPS bootstrap resolver for its own control connectivity, so failure of ordinary DNS alone does not imply that all daemon connectivity fails. No claim that every Tailscale provisioning method requires a live browser or ordinary DNS.
Public sources
- https://tailscale.com/docs/concepts/tailscale-identity
- https://tailscale.com/docs/install/linux
- https://tailscale.com/docs/features/access-control/auth-keys
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round590-sources.json
- round594.html
- round594-sources.json