fix: Use correct DNS caching for SNI to function properly #1934

Merged
nex merged 5 commits from s1lv3r/continuwuity:zoe/fix-resolver-caching into main 2026-07-10 13:45:00 +00:00
Member

This removes the old (broken) DNS caching method for reqwest, and replaces it with resolvematrix' MatrixDnsResolver, as it correctly implements caching and overrides for correct SNI behavior.

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
This removes the old (broken) DNS caching method for reqwest, and replaces it with resolvematrix' `MatrixDnsResolver`, as it correctly implements caching and overrides for correct SNI behavior. **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages
fix: Use correct DNS caching for SNI to function properly
Some checks failed
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 4s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 56s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m17s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 2m39s
2883ebda04
This removes the old (broken) DNS caching method for reqwest, and replaces
it with resolvematrix' `MatrixDnsResolver`, as it correctly implements
caching and overrides for correct SNI behavior.
chore: Add changelog
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Update flake hashes / update-flake-hashes (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
4cc2e2498e
chore: Update resolvematrix dependency rev hash
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 55s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m17s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m21s
b4b96fffb3
s1lv3r changed title from fix: Use correct DNS caching for SNI to function properly to WIP: fix: Use correct DNS caching for SNI to function properly 2026-07-10 00:19:38 +00:00
Author
Member

Before merge, a new version of resolvematrix will have to be released and cargo.toml must be changed to reflect this instead of a git hash

Before merge, a new version of resolvematrix will have to be released and cargo.toml must be changed to reflect this instead of a git hash
Author
Member
Blocked by https://forgejo.ellis.link/continuwuation/resolvematrix/pulls/30
chore(deps): Update to resolvematrix 1.1.0
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 56s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m21s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m30s
b43b6a7864
s1lv3r changed title from WIP: fix: Use correct DNS caching for SNI to function properly to fix: Use correct DNS caching for SNI to function properly 2026-07-10 00:58:54 +00:00
ginger approved these changes 2026-07-10 01:01:34 +00:00
@ -0,0 +1 @@
Replace old DNS cache with resolvematrix' built in one for better handling of SNI and overrides. Contributed by @s1lv3r.
Owner

I don't think this needs a changelog tbh

I don't think this needs a changelog tbh
Author
Member

I disagree, it changes the DNS caching entirely, its a decently big change

I disagree, it changes the DNS caching entirely, its a decently big change
Owner

this probably isn't the correct way to describe it to end users, then.

this probably isn't the correct way to describe it to end users, then.
nex marked this conversation as resolved
chore: Update changelog
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m3s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m18s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 7m43s
c4278c65b1
@ -257,0 +297,4 @@
opts.timeout = Duration::from_secs(config.dns_timeout);
opts.attempts = config.dns_attempts.into();
opts.try_tcp_on_error = config.dns_tcp_fallback;
opts.num_concurrent_reqs = 1;
Owner

only 1 concurrent request?

only 1 concurrent request?
Owner

nvm that's from the old code diff is messing with me

nvm that's from the old code diff is messing with me
nex marked this conversation as resolved
nex approved these changes 2026-07-10 13:10:26 +00:00
nex merged commit bed80964fd into main 2026-07-10 13:45:00 +00:00
nex deleted branch zoe/fix-resolver-caching 2026-07-10 13:45:00 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!1934
No description provided.