Skip to content
TheChatArchiveThe Chat Archive
x-ai/grok-4.5· unknownHugging 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. Assistant

    I'll start by exploring the repository structure and searching for DNS-related code, especially around split DNS and app connectors.

  3. Assistant

    Let me search for DNS configuration and app connector related code.

  4. Assistant

    I'll inspect how DNS configuration decides to register with the OS, focusing on split DNS and app connectors.

  5. Assistant

    Let me look at how DNS config is built - particularly related to app connectors and when OS DNS is configured.

  6. Assistant

    There's a dnsconfig related test. Let me look at the dnsConfigForNetmap function and the relevant test cases about app connectors.

  7. Assistant

    Let me find the dnsConfigForNetmap function definition.

  8. Assistant

    Found it in node_backend.go. Let me read that function and also the OS DNS setup logic.

  9. Assistant

    Let me continue reading the rest of dnsConfigForNetmap.

  10. Assistant

    Let me continue reading and also look at how manager decides to configure OS DNS.

  11. Assistant

    Let me inspect the app connector split DNS peer selection and compileConfig logic more carefully.

  12. Assistant

    Let me continue reading compileConfig - especially the part about app connectors.

  13. Assistant

    Let me check recent git history and the app-connector DNS tests for clues.

  14. Assistant

    Let me look at git log for DNS-related commits that might relate to this bug, and also look at resolved.go for systemd-resolved.

  15. Assistant

    Let me search for relevant issues/comments and inspect how AcceptDNS interacts with OS registration.

  16. Assistant

    Let me look at how resolved handles split DNS and also check if there's something about empty MatchDomains issus. Also let me look at when Control plane sends routes for app connectors.

  17. Assistant

    Let me look more carefully. When MagicDNS is off and there's split DNS from app connectors:

  18. Assistant

    Let me look at manager_test.go for test cases that might relate to this, and also PickSplitDNSPeers.

  19. Assistant

    Let me look at the manager test for "routes-split" which seems to match this scenario.

  20. Assistant

    Looking at routes-split - when all routes go to same resolver and split is supported, OS gets MatchDomains. That should work. I think the core issue is in how the client registers split DNS with the OS when using an app connector.

  21. Assistant

    Let me look for PRs or recent changes about this specific bug.

  22. Assistant

    Let me look at the SetDNS path more carefully and whether empty OSConfig is applied. Also maybe looking at health checks or DNS status.

  23. Assistant

    Let me read the Manager.Set method and how OS config is applied.

  24. Assistant

    Let me look at singleResolverSet and toIPsOnly more carefully - HTTP/DoH resolvers may be the problem.

  25. Assistant

    I think I found the bug. When split DNS routes only use HTTP/DoH peer API resolvers (app connectors), singleResolverSet() is non-empty but toIPsOnly strips them, leaving empty nameservers. Verifying with tests.

  26. Assistant

    Let me search for tests covering split DNS routes that use only DoH URLs.

  27. Assistant

    I'll reproduce the bug with a small test script, then apply a fix.

  28. Assistant

    I'll temporarily add a failing test case to reproduce the bug, then fix it.

  29. Assistant

    I'll add a temporary failing test case and run it to confirm the bug.

  30. Assistant

    I accidentally duplicated a closing brace — fixing that now.

  31. Assistant

    Good. Now let me run the specific test to reproduce.

  32. Assistant

    Need to set up the Go environment.

  33. Assistant

    There's a custom go toolchain in tool/. Let me check how to run tests properly.

  34. Assistant

    Need to set HOME.

  35. Assistant

    Good, now run the test.

  36. Assistant

    Confirmed the bug. Checking how IPPort handles bare IPs, then applying the fix.

  37. Assistant

    Applying the fix to compileConfig so we only hand resolvers to the OS when they're plain IPs.

  38. Assistant

    I'll apply the fix now.

  39. Assistant

    There's a subtle issue: MagicDNS routes with empty resolvers are forums stripped into LocalDomains before singleResolverSet is called - wait, no:

  40. Assistant

    All manager tests pass. Removing the temporary test I added, per the instructions.

  41. Assistant

    I accidentally edited the wrong file — restoring manager.go and cleaning up the test file.

  42. Assistant

    I lost the fix on manager.go — reapplying it and removing the test.

  43. Assistant

    Restored manager.go to its original state. Re-applying the fix carefully.

  44. Assistant

    Verifying the fix with a temporary external test and running the suite.

  45. Assistant

    Existing tests pass. I'll carefully re-add a temporary test to double-check the fix, then remove it.

  46. Assistant

    The fix works. Removing the temporary test and running the full net/dns suite.

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