rewindex

CompaniesTailscaleIncidents

Tailscale: Funnel hostnames not resolving in public DNS

MinorStatus: monitoringeditedStarted Not resolved2 updatesstatus.tailscale.com (opens in new tab)

Affected components: Funnel

Timeline of updates

  1. investigating

    We are currently investigating reports of Funnel hostnames not resolving publicly.

    Affected devices show Funnel as enabled and have valid HTTPS certificates, but public DNS lookups for the device's ts.net: http://ts.net (opens in new tab) name return no address, and external access does not work. In some cases the records appear after a delay.

    Connectivity from within the tailnet, including MagicDNS and Serve, is not affected.

  2. monitoring

    We have rolled out a configuration change, and are now seeing public Funnel DNS records created normally. We will continue to monitor to ensure DNS records remain stable.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.tailscale.com (opens in new tab).

Tailscale profileRecent Tailscale incidentsMarkdownJSON