AdguardTeam / AdguardTeam/dnsproxy

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

Abierto
#452 0 comentarios 2 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Go
Estrellas
3.3k
Forks
343
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.