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 code related to split DNS and app connectors.

  3. Assistant

    Let me search for code related to split DNS and app connectors.

  4. Assistant

    rg is not available, let me use grep.

  5. Assistant

    Let me dig into DNS configuration and OS registration logic.

  6. Assistant

    Let me examine DNS configuration and how app connectors affect split DNS.

  7. Assistant

    There's a conn25-split-dns test — let me examine the DNS config building logic.

  8. Assistant

    Let me look at the dnsConfigForNetmap function and how MagicDNS/split DNS interacts with OS configuration.

  9. Assistant

    Let me continue reading the dnsConfigForNetmap function, especially around routes and CorpDNS.

  10. Assistant

    I see CorpDNS false returns early — let me check the rest of the function and the conn25 tests.

  11. Assistant

    The early return when CorpDNS is off skips app connector routes — I'll verify that against OS DNS programming logic.

  12. Assistant

    Let me look at how the manager converts Config to OSConfig and when it decides not to configure OS DNS.

  13. Assistant

    Let me examine compileConfig and the conn25-related DNS tests.

  14. Assistant

    Let me look at the conn25 tests and related code to understand the intended behavior.

  15. Assistant

    Let me search the git history and docs for related bug fixes around app connector split DNS.

  16. Assistant

    Let me check how classic app connectors and systemd-resolved handle split DNS registration.

  17. Assistant

    Let me look at the classic app connector and how split DNS domains get into the DNS config from the control plane.

  18. Assistant

    Let me search for related comments and how Apple/iOS handles app connectors with split DNS.

  19. Assistant

    DoH-style app connector resolvers may not map to IPs — I'll inspect how they are handled.

  20. Assistant

    Found a likely bug: DoH resolvers yield empty Nameservers. Checking singleResolverSet and related tests.

  21. Assistant

    Let me look at the manager test cases around routes-only split DNS and understand the expected behavior when resolvers are non-IP.

  22. Assistant

    That matches the issue: with MagicDNS off, DoH split routes take the OS path and yield empty Nameservers. Checking sameResolverNames and related tests.

  23. Assistant

    Confirming systemd-resolved supports split DNS, then applying the fix.

  24. Assistant

    I'll fix compileConfig so non-IP (DoH) resolvers fall through to the quad-100 path instead of registering empty nameservers.

  25. Assistant

    Updating the condition to only hand off plain IP:53 resolvers to the OS.

  26. Assistant

    Cleaning up the comment and writing a temporary test to verify the fix.

  27. Assistant

    I'll inspect the manager test helpers, then add a temporary test for the app-connector DoH path.

  28. Assistant

    I'll write a temporary test outside the package and run the existing manager tests.

  29. Assistant

    Creating a temporary test to verify the fix, then removing it.

  30. Assistant

    Writing a proper temporary test file.

  31. Assistant

    Checking the temp test file and running it.

  32. Assistant

    Need to figure out the Go environment setup.

  33. Assistant

    I should use ./tool/go to run tests.

  34. Assistant

    Need to set HOME.

  35. Assistant

    Need to mirror how TestManager constructs the Dialer.

  36. Assistant

    Rewriting the temp test to follow the TestManager pattern.

  37. Assistant

    The temp test passed. Running the full manager test suite and removing the temp test.

  38. Assistant

    Verifying the final diff and whether any other edge cases remain.

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