Commit c4879a2
committed
Trim unneeded entries
These servers never supported the DNSCrypt v2 protocol, and have
been a pain to maintain compatibility with. But the main issue
is that in some countries, they are now lying resolvers, *except*
for the certificate.
That makes it difficult to reliably detect that they are lying
resolvers. From a user perspective in these countries, it appears
that DNS queries randomly fail, when they are hitting these servers.
I tried to think of different ways to detect this, but couldn't
find anything satisfactory.
Maybe if they properly implement the DNSCrypt protocol some day,
they will take it as an opportunity to also fix that bug, and
return consistent error codes, even for the certificates.1 parent 8987906 commit c4879a2
2 files changed
+1
-6
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
154 | 154 | | |
155 | 155 | | |
156 | 156 | | |
157 | | - | |
158 | 157 | | |
159 | 158 | | |
160 | 159 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
774 | 774 | | |
775 | 775 | | |
776 | 776 | | |
777 | | - | |
778 | | - | |
779 | | - | |
780 | | - | |
781 | 777 | | |
782 | 778 | | |
783 | 779 | | |
784 | 780 | | |
785 | 781 | | |
786 | 782 | | |
787 | 783 | | |
788 | | - | |
| 784 | + | |
789 | 785 | | |
790 | 786 | | |
791 | 787 | | |
| |||
0 commit comments