Skip to content
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

Switch to hickory-resolver for DNS queries #557

Open
aumetra opened this issue Jul 12, 2024 · 0 comments
Open

Switch to hickory-resolver for DNS queries #557

aumetra opened this issue Jul 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@aumetra
Copy link
Member

aumetra commented Jul 12, 2024

Is your feature request related to a problem? Please describe.

DNS queries are currently done using the standard system resolver, which means that for each time a domain name is resolved, we use a tokio blocking thread under the hood to invoke a system call.
This works well to some extent but at some point this can become a bottleneck, especially in ActivityPub environments, where there is a lot of different domain names that have to be resolved quite often.

Describe the solution you'd like

The hickory-dns project provides a user-land async Rust implementation of the DNS protocol.
This would allow us to keep all the resolve logic in-process. And due to it being async from the ground up, we don't need to spawn any blocking threads, getting rid of the expensive inter-thread communication and thread spawning.

It would also allow us to easier support:

  1. DNS-over-TLS and DNS-over-HTTPS
  2. Non-system DNS resolvers (for example, the system uses the default ISP-provided DNS servers, while Kitsune uses Quad9)
@aumetra aumetra added the enhancement New feature or request label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant