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
Extremely slow resolution on Windows #1968
Comments
Set up a basic tracing-subscriber to get a feel for which part is slow? Investigate what the system config amounts to on this system? |
We've had other reports of trust-dns cycling through interfaces on Windows. We don't have a lot of folks contributing to the project from Windows, so it's sadly not as well supported as macOS and Linux. If you do have some time to investigate this, that would be really helpful to this project! |
Note that this can be worked around by specifying a different resolver. The mongodb crate readme has an example. |
I’m also running into this issue, I will do some investigating when I have some time |
Are you sure this can be reproduced? I don't seem to have encountered this problem, it has always been faster. You can download this program from here and see if it is too slow. |
Yes, this sounds like exactly what others have noticed. I don't know what the "fix" is as I'm not using Windows and can't investigate. If you have a proposed change you'd like to put forward in a PR, I think we'd all be grateful. |
I'd suggest we should use something more like a deny list than an allow list here, to avoid unpleasant surprises? I think it makes sense to require |
I agree, I'm not sure if there is some generally accepted method of choosing which adapters to use in Windows-land. In regard to Tailscale on Windows it comes up as an "Unsupported" type adapter and not a virtual adapter so it wasn't impacted by the virtual adapter exclusions but by the Ethernet and Wifi exclusions. Your point still stands though. It is still surprisingly slow if you still have the WSL adapter in the adapter list though. I also believe that depending on the Windows install/users machine hardware and software installed there will be varying names for virtual adapters so it's hard to just disable them all. |
Describe the bug
On my machine,
TokioAsyncResolver
takes a very long time to resolve any DNS record - up to a minute! - regardless of domain, record type, or configured DNS servers in Windows. I don't even know why this is happening, because I can't actually repro it on my other machines - only on this specific Windows machine (Linux machines on same network work fine). I encountered this from a library I was using that depends ontrust_dns_resolver
. I'm mainly posting this in hopes that anyone has idea for better debugging steps so we can work it out together.To Reproduce
Expected behavior
Not take 20.046 seconds to resolve rust-lang.org.
System:
Version:
Crate: trust_dns_resolver
Version: 0.22.0
The text was updated successfully, but these errors were encountered: