-
-
Notifications
You must be signed in to change notification settings - Fork 967
[client] Use Go's resolver for darwin for control plane and ICE traffic #4833
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| package net | ||
|
|
||
| import ( | ||
| "net" | ||
| "os" | ||
| "runtime" | ||
| "strings" | ||
|
|
||
| log "github.com/sirupsen/logrus" | ||
| ) | ||
|
|
||
| const ( | ||
| // EnvResolver is the environment variable to control DNS resolver behavior | ||
| // Values: "system" (use system resolver), "go" (use pure Go resolver), empty (auto-detect) | ||
| EnvResolver = "NB_DNS_RESOLVER" | ||
| ) | ||
|
|
||
| // NewResolver creates a DNS resolver with appropriate settings based on platform and configuration. | ||
| // On Darwin (macOS), it defaults to the pure Go resolver to avoid getaddrinfo hangs after sleep/wake. | ||
| // This is particularly important for connections using this package's Dialer, which bypasses the NetBird | ||
| // overlay network for control plane traffic. Since these connections target external infrastructure | ||
| // (management, signal, relay servers), it is safe to ignore split DNS configurations that would | ||
| // normally be provided by the system resolver. | ||
| // On other platforms, it uses the system resolver (cgo). | ||
| // This behavior can be overridden using the NB_DNS_RESOLVER environment variable or GODEBUG. | ||
| func NewResolver() *net.Resolver { | ||
| if resolver := os.Getenv(EnvResolver); resolver != "" { | ||
| switch strings.ToLower(resolver) { | ||
| case "system": | ||
| return net.DefaultResolver | ||
| case "go": | ||
| return &net.Resolver{ | ||
| PreferGo: true, | ||
| } | ||
| default: | ||
| log.Debugf("Invalid %s value: %s, using platform defaults", EnvResolver, resolver) | ||
| } | ||
| } | ||
|
|
||
| if runtime.GOOS == "darwin" { | ||
| return &net.Resolver{ | ||
| PreferGo: true, | ||
| } | ||
| } | ||
|
|
||
| return net.DefaultResolver | ||
| } | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify the split DNS assumption for control plane traffic.
The comment states it's "safe to ignore split DNS configurations" for control plane traffic because these connections "target external infrastructure." However, in enterprise or self-hosted scenarios, management/signal/relay servers may be internal resources that rely on split DNS. Users with private deployments behind split DNS could experience connectivity issues.
Consider documenting this limitation or adding a configuration option for environments where control plane servers are internal.
Length of output: 1472
🏁 Script executed:
Length of output: 15091
🏁 Script executed:
Length of output: 174
🏁 Script executed:
Length of output: 6138
Update documentation to guide users on split DNS scenarios in enterprise deployments.
The concern about split DNS is valid. While the code provides override via
NB_DNS_RESOLVER=systemenvironment variable, the documentation doesn't explain when or why users should use it. In self-hosted or enterprise deployments where management/signal/relay servers are internal and rely on split DNS, users will encounter connectivity issues without knowing how to resolve them.Recommended improvements:
NB_DNS_RESOLVER=systemshould be used for deployments with internal servers behind split DNSGODEBUGoverride does and provide an exampleThis allows users to self-serve when they encounter the issue rather than discovering it only through trial and error.
🤖 Prompt for AI Agents