DNS resolver configuration for internal HTTP client lookups #5355
+332
−4
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
jmwample
added a commit
that referenced
this pull request
Jan 21, 2025
jstuczyn
reviewed
Jan 22, 2025
|
It's strange to see that CI is not being triggered, I don't know what the issue is. Not seeing any failed triggered builds in the action tab either |
jmwample
force-pushed
the
jmwample/dot
branch
from
0773119 to
32e39eb
Compare
octol
reviewed
Jan 22, 2025
octol
reviewed
Jan 22, 2025
octol
approved these changes
Jan 23, 2025
jstuczyn
approved these changes
Jan 23, 2025
jmwample
added a commit
that referenced
this pull request
Jan 23, 2025
jmwample
added a commit
that referenced
this pull request
Jan 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 resolver itself is the set combination of the google, cloudflare, and quad9 endpoints supporting DoH, DoT, and for google DoH3 as well.
This resolver implements a fallback mechanism where, should the DNS-over-X resolution fail, a followup resolution will be done using the hosts configured default (e.g.
/etc/resolve.confon linux).This change is