Add DNS override to proxyrouter service - #44
Open
bconik wants to merge 1 commit into
Open
Conversation
The chrome service already sets an explicit DNS resolver (8.8.8.8/1.1.1.1) to work around Docker setups where the embedded resolver isn't reliably reachable (e.g. rootless Docker with a VM-based network stack). proxyrouter never got the same override, even though it's the service that actually resolves every proxied request's target host. Without working DNS in proxyrouter, requests fail (intermittently or entirely depending on the environment) with generic connection errors that give no indication DNS is the cause.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The
chromeservice already sets an explicit DNS resolver (8.8.8.8/1.1.1.1) to work around Docker setups where the embedded resolver isn't reliably reachable (e.g. rootless Docker with a VM-based network stack).proxyrouternever got the same override, even though it's the service that actually resolves every proxied request's target host.Without working DNS in
proxyrouter, requests fail — intermittently or entirely depending on the environment — with generic connection errors that give no indication DNS is the cause. This mirrorschrome's existing override for consistency.