-
Notifications
You must be signed in to change notification settings - Fork 221
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
feat(peerseeds/autoupdate): hickory-dns upgrade, default to system DNS #6600
feat(peerseeds/autoupdate): hickory-dns upgrade, default to system DNS #6600
Conversation
1e7a4b7
to
ffeb16a
Compare
5ac92ec
to
51c3bf5
Compare
Test Results (Integration tests) 2 files 11 suites 32m 27s ⏱️ For more details on these failures, see this check. Results for commit 6f60db1. ♻️ This comment has been updated with latest results. |
Test Results (CI) 3 files 129 suites 35m 45s ⏱️ Results for commit 6f60db1. ♻️ This comment has been updated with latest results. |
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.
pending ci
f7e8f64
to
be6dd94
Compare
Looks like we're using an old version of gcc CI. I've added that to the CI deps install script so let's see. |
be6dd94
to
6f60db1
Compare
Guess not - I've removed the |
Description
Upgrade from trust dns to hickory DNS
Allow system default DNS to be used for DNS resolution
Motivation and Context
Cloudflare 1.1.1.1 was used by default and this can be blocked. Better UX to use the system default.
How Has This Been Tested?
Existing tests updated
What process can a PR reviewer use to test or verify this change?
Seed peers still work
Breaking Changes