fix(dns): improve DNS server reliability and compatibility #998
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.
Fixes #817, #696, #834
Type of Change
Motivation and Context
The DNS server now binds to network gateway addresses instead of only localhost, allowing containers to resolve hostnames correctly across different network configurations. This also fixes stale nameserver detection after network migration by refreshing resolvers when the network changes. A new --dns-tcp flag forces TCP for DNS queries on unreliable networks, and host search domains are now inherited for compatibility with Tailscale and other VPN configurations.
Testing