Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-sonnet-5· anthropicHugging 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

    Interface

    No new interfaces are introduced.

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

    Now let's add a helper function to check if resolvers are all plain IP:port resolvers usable by OS split DNS, and use it in manager.go.

  3. Claude Assistant

    Need blank line before matchDomains comment.

  4. Claude Assistant

    Now update manager.go to use this helper.

  5. Claude Assistant

    There's a duplicate closing brace at line 380. Let's fix.

  6. Claude Assistant

    Now let's build.

  7. Claude Assistant

    Build succeeds. Now let's run the dns package tests.

  8. Claude Assistant

    Existing tests pass. Now let's also check ipnlocal tests build/pass since we didn't change that file, but let's verify config.go compiles fine everywhere.

  9. Claude Assistant

    Good, let's redo repro test using fakeOSConfigurator properly, and a minimal Manager literal without health tracker complexity (health field can maybe be nil? Let's check if compileConfig uses m.health).

  10. Claude Assistant

    Let's rewrite the repro test to use NewManager similar to existing tests.

  11. Claude Assistant

    Let's confirm the bug existed before the fix by temporarily stashing changes.

  12. Claude Assistant

    This confirms the bug and the fix. Now let's remove the temporary repro test file and run the full test suite once more.

  13. Claude Assistant

    Whole repo builds fine. Let's also run the broader test suite for ipn/ipnlocal DNS-related tests to double check nothing regressed there (since node_backend.go logic feeds into this).

  14. Claude Assistant

    Now let's view the final diff for review.

  15. Claude Assistant

    Good, publicdns already imported. Let's update allSimpleResolvers to match the same rigor.

  16. Claude Assistant

    Let's revert manager.go to clean state and redo this properly - remove the corrupted setLocked function, then move the allSimpleResolvers definition to config.go instead.

  17. Claude Assistant

    Now let's redo the edits cleanly, this time using --file explicitly to avoid ambiguity.

  18. Claude Assistant

    Need blank line before matchDomains comment again.

  19. Claude Assistant

    Good, config.go is clean now. Now let's edit manager.go using --file explicitly.

  20. Claude Assistant

    This looks correct now. Let's build and test again.

  21. Claude Assistant

    Now let's re-run the repro test to confirm the fix still works with the added port/53 and DoH-only-IP check.

  22. Claude Assistant

    Both scenarios work correctly - the app connector case now routes through quad-100, and the plain IP split DNS case still uses the fast OS-native path. Let's remove the temporary test file and run the full test suite once more.

  23. Claude Assistant

    All tests pass. Let's view final diff.

  24. Claude Assistant

    Clean diff, no leftover temp files.

  25. Claude Assistant

    No formatting issues. Now let's go through the checklist.

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