-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Don't use the system default resolver implicitly #647
Comments
May be relevant: golang/go#12503 |
Here's what I see on first run:
We shouldn't load filters unless AGH DNS server is running. |
And here's the second issue: handle DNS host=0.0.0.0 -- use 127.0.0.1 in this case. |
Fixed |
I had to roll it back due to the Docker-related issue: See some details here: Also, I just realized that we're passing |
False alarm :) |
There're a couple of places in the code where we use system default resolver implicitly:
Ideally, we should avoid doing it. But I don't like the idea of propagating the custom resolver to every place where we make a http request. Can we somehow change the default resolver globally?
The text was updated successfully, but these errors were encountered: