# Tailscale: Funnel hostnames not resolving in public DNS

- Impact (vendor’s label): minor
- Status: monitoring · edited after publishing
- Started: 2026-10-24 17:23 UTC · Resolved: not resolved · Duration: ongoing
- Updates: 2 · Affected components: Funnel
- [Vendor status page: https://status.tailscale.com/incidents/01M5QF0RTE57V3E47CK2HQREK0](https://status.tailscale.com/incidents/01M5QF0RTE57V3E47CK2HQREK0)
- [Company: Tailscale](https://rewindex.com/company/tailscale.md)

## Timeline of updates

- **investigating** 2026-10-24 17:23 UTC: 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 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.
- **monitoring** 2026-10-24 19:52 UTC: 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.

## Rewindex changes for this incident

- 2026-10-24 19:53 UTC: [Incident updated: Funnel hostnames not resolving in public DNS](https://rewindex.com/change/r2682f93fb3fdbd.md)


---
Canonical: https://rewindex.com/company/tailscale/incidents/01M5QF0RTE57V3E47CK2HQREK0 · Markdown: https://rewindex.com/company/tailscale/incidents/01M5QF0RTE57V3E47CK2HQREK0.md · JSON: https://rewindex.com/api/v1/companies/tailscale/incidents/01M5QF0RTE57V3E47CK2HQREK0 · Generated 2026-10-25T09:07:01.713Z