No split dns registered with the OS with an app connector. What is the issue? It's…
- User
No split dns registered with the OS with an app connector.
What is the issue?
It's possible to have an app connector but tailscale fails to register split dns with the OS to route dns requests to it.
Steps to reproduce
Linux w/ systemd-resolved Turn off MagicDNS No global dns fallback results in Tailscale not being used for DNS by the operating system
Are there any recent changes that introduced the issue?
No response
OS
No response
OS version
No response
Tailscale version
No response
Other software
No response
Bug report
No response
Interface
No new interfaces are introduced.
- Assistant
I’ll trace the DNS configuration path for app connectors, identify why an empty global resolver set suppresses OS split-DNS registration, then patch and run focused tests.
- Assistant
The worktree is clean.
rgisn’t installed here, so I’m switching to repository-nativegit grepand narrowing in on DNS manager/config generation tests. - Assistant
The failure is in DNS compilation, after the app-connector route is correctly created. With MagicDNS off, that route is the only resolver set; Linux’s split-DNS fast path tries to hand its HTTP peer-API resolver directly to systemd-resolved, but conversion yields zero IP nameservers. I’m adding a regression case and constraining that fast path to resolver addresses the OS can actually consume.
- Assistant
The focused regression is now in place. The implementation routes non-OS-compatible resolver forms (including the app connector’s HTTP DNS endpoint) through Tailscale’s local DNS proxy while still registering the domain with systemd-resolved; I’m waiting on the focused package tests and will inspect the final diff afterward.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.