Incidentsby GlyphFunnel hostnames not resolving in public DNS
Oct 27, 14:16 UTCOngoing
Duration
Ongoing
Impact
Minor
Root cause
Not disclosed
Tailscale, 90 days
19 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Investigating · Oct 27, 14:16 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 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.
More from Tailscale
Full historyFunnel hostnames not resolving in public DNSlasted 41h 44mAdmin Panel Login Issueslasted 6mFunnel performance degradationlasted 2h 55mCoordination service issueslasted 44mIru (formerly Kandji) device posture integration failurelasted 2h 13mSCIM groups not being updated for secondary tailnets in multi tailnet organizationslasted 29m