AdguardTeam / AdguardTeam/dnsproxy

Is sorting of upstreams (fastest->slowest) really working correct?!

Ouverte
#452 0 commentaires 2 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Go
Étoiles
3.3k
Forks
343
Métriques de merge des PR
Aucune PR mergée en 30 j

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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.