Replies: 2 comments 4 replies
-
I learnt the code about anonymized DNS relays. |
Beta Was this translation helpful? Give feedback.
4 replies
-
Thank you! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I recently experienced frequent but intermittent resolution failure (timeouts). I checked the logs, and when resolution was failing, I saw "SERVER_TIMEOUT" errors, from a variety of different servers. The same servers, however, would eventually start working again, with no action on my part. It seemed strange that there would be so much outage among the standard servers (I'm using the default list), and I eventually realized that the problem was not actually with the servers, but with one of my relays - I'm using Anonymized DNS, and one of my specified relays,
anon-plan9-dns
, had gone down (link, link).I understand that the fact that DNScrypt / Anonymized DNS uses UDP makes it hard to distinguish between an unresponsive resolver and an unresponsize relay, but I think it would be useful if dnscrypt-proxy included some kind of check to see if the relay is responsive, at least upon encountering (repeated) SERVER_TIMEOUTs. Reporting SERVER_TIMEOUT when the issue is with a relay can be somewhat misleading.
Beta Was this translation helpful? Give feedback.
All reactions