AdguardTeam / AdguardTeam/dnsproxy

Getting multiple Reading response length: 0-RTT rejected errors.

Aperta
#492 2 commenti 0 reazioni 1 assegnatario Rivendicata da @EugeneOne1 Vedi su GitHub
enhancement
Lingua principale
Go
Stelle
3.3k
Fork
343
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Compiled from the latest main branch and been using it for couple weeks. Im running two instances on the machine one with caching and one without and both are throwing this error. Please advise!

2026/03/24 17:25:45.172454 ERROR exchange failed prefix=dnsproxy upstream=quic://p0.freedns.controld.com:853 question=";sc3.rbxcdn.com.\tIN\t A" duration=196.110457ms err="from quic://p0.freedns.controld.com:853: reading response length: 0-RTT rejected"
2026/03/24 17:26:22.622782 ERROR exchange failed prefix=dnsproxy upstream=quic://p0.freedns.controld.com:853 question=";rewarded-video.roblox.com.\tIN\t HTTPS" duration=53.441964ms err="from quic://p0.freedns.controld.com:853: reading response length: 0-RTT rejected"

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.