AdguardTeam / AdguardTeam/dnsproxy

Bug Report: upstream doh queries use random tls v1.2 or v1.3 for different servers

Ouverte
#509 0 commentaires 0 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

dnsproxy v0.82.0, Windows 11
Upstreams: IP-based DoH (no SNI), e.g. https://149.112.112.9/dns-query

Problem:
After observing random fails on accessing DoH servers, I have found out
dnsproxy negotiates TLS 1.2 with certain DoH upstreams despite those servers supporting TLS 1.3.
Setting tls-min-version: 1.3 in config has no effect on outgoing upstream connections.

Key finding:
Using a 3rd party tool, querying the exact same server, negotiates TLS 1.3 successfully. Confirmed via Wireshark on both sides. This rules out the server and points to a difference in how dnsproxy initializes its upstream HTTP client.
Expected behavior
dnsproxy should negotiate TLS 1.3 with upstreams that support it, consistent with dnslookup behavior.

Request:
Please add the ability to determine upstream tls version

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.