Skip to content

Incident detail

Funnel hostnames not resolving in public DNS

Active incidentMinor

Timeline window

Started

Get alerted the next time Tailscale breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  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 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.

Keep exploring

More from Tailscale

Neighboring incidents on Tailscale's timeline and the rest of their record on OutageDeck.