Skip to content
TheChatArchiveThe Chat Archive
gpt-5.6-luna· openaiHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION No split dns registered with the OS with an app connector. What is the…

  1. User

    ISSUE DESCRIPTION

    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

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /tailscale, current file: none) bash-$

  2. Assistant

    I’ll trace the DNS configuration path for app connectors, especially Linux/systemd-resolved behavior when MagicDNS and global fallback are disabled. I’ll inspect relevant code and tests, identify why app-connector routes don’t trigger split DNS registration, implement the smallest general fix, then run focused tests and review the diff.

  3. Assistant

    The failure is in net/dns.Manager.compileConfig: app-connector routes use a PeerAPI DoH URL, but the “single resolver set” optimization assumes every resolver is a plain IP:port-53 server. It calls toIPsOnly, which drops the DoH URL while still leaving MatchDomains, producing a split-DNS config with no nameserver for systemd-resolved. I’ll restrict that optimization to route sets consisting entirely of plain port-53 IP resolvers; custom resolvers will use quad-100, preserving the routes internally while registering a usable OS nameserver and split domains.

  4. Assistant

    The code change is in place and focused tests pass after setting the Go cache environment. The important fallback behavior is now: plain IP resolvers still use native split DNS unchanged; URL/custom-port resolvers skip that path, retain their routes in the internal resolver, and reach the quad-100 split-DNS path. I’ll run the complete affected package tests and inspect formatting/status before submission.

  5. Assistant

    Verification is complete: both affected Go packages pass all existing tests, git diff --check reports no whitespace errors, and only net/dns/manager.go is modified. The fix also handles mixed route sets conservatively: if routes do not all share a directly usable IP:53 resolver set, quad-100 is used rather than risking an incomplete OS configuration. I’ll now submit the change.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.