Open blinkingbee opened 4 years ago
That's really interesting - could you share what version of DNSCrypt-Proxy you have, please? I suspect that it's more recent than my release.
I'm using Dnscrypt-proxy v 2.0.44 https://github.com/DNSCrypt/dnscrypt-proxy/releases/tag/2.0.44
Have documented in the file; thanks!
Confirming what appears to be the canonical location for this data:
The README for the DNSCrypt/dnscrypt-resolvers repository states:
Stable download URLs:
There, we find that the public-resolvers.md file, itself, states:
To use that list, add this to the
[sources]
section of yourdnscrypt-proxy.toml
configuration file:[sources.'public-resolvers'] urls = ['https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v3/public-resolvers.md', 'https://download.dnscrypt.info/resolvers-list/v3/public-resolvers.md'] minisign_key = 'RWQf6LRCGA9i53mlYecO4IzT51TGPpvWucNSCh1CBM0QTaLn73Y7GFO3' cache_file = 'public-resolvers.md'
Platform: Raspberry Pi - Buster Lite
Using your commit of 3 July I get an error:
Process: 6483 ExecStart=/opt/dnscrypt-proxy/dnscrypt-proxy -config dnscrypt-proxy.toml (code=exited, status=255/EXCEPTION).
Changing [sources.'public-resolvers'] to v3 as in : urls = ['https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/**v3**/public-resolvers.md', 'https://download.dnscrypt.info/resolvers-list/**v3**/public-resolvers.md']
fixes the problem.
I'm very much a newbie on this so on a fairly steep learning curve.
Incidentally regarding latency, the best I can manage here in Adelaide, Australia is around 465ms which probably reflects the fact that TOR exit nodes are mostly in Europe or US.