AdguardTeam / AdguardTeam/dnsproxy
Is sorting of upstreams (fastest->slowest) really working correct?!
Open
- Dominant language
- Go
- Stars
- 3.3k
- Forks
- 343
- PR merge metrics
- No merged PRs in 30d
Description
I suspect that the new logic implemented a few months ago to sort DNS-servers (fastest->slowest) might have a bug?!
As a test I added two slow DNS-servers far away with DNS-answers always in the range 60-120 ms and let it run for 24 hours. Totally 10 upstream servers in the list for DNSProxy to choose from. The strange is that DNSProxy selects these two servers for most queries, so I wonder if the sorting is reversed or weighted/randomized wrong. Seems that the slowest servers gets most queries and the fastest (5-20 ms) is at the bottom in the list.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.