Dnscrypt-proxy

[vasek00]

Возможно ли поднять Dnscrypt-proxy c текущего 2.0.27 до 2.0.31

Скрытый текст

2.0.31

• This version fixes two regressions introduced in version 2.0.29: DoH server couldn't be reached over IPv6 any more, and the proxy couldn't be interrupted while servers were being benchmarked.

2.0.30

• This version fixes a startup issue introduced in version 2.0.29, on systems for which the service cannot be automatically installed (such as OpenBSD and FreeBSD). Reported by @5ch17 and Vinícius Zavam, and fixed by Will Elwood, thanks!

2.0.29

• Support for Anonymized DNS has been added!
• Wait before stopping, fixing an issue with Unbound (thanks to Vladimir Bauer)
• DNS stamps are now included in the -list-all -json ouptut
• The netprobe_timeout setting from the configuration file or command-line was ignored. This has been fixed.
• The TTL or cloaked entries can now be adjusted (thanks to Markus Linnala)
• Cached IP address from DoH servers now expire (thanks to Markus Linnala)
• DNSCrypt certificates can be fetched over Tor and SOCKS proxies
• Retries over TCP are faster
• Improved logging (thanks to Alison Winters)
• Ignore non-TXT records in certificate responses (thanks to Vladimir Bauer)
• A lot of internal cleanups, thanks to Markus Linnala

2.0.29-beta.3

• Improved logging
• Added a workaround for DNS servers using a non-standard provider name.

2.0.29-beta.2

• Support for Anonymized DNSCrypt has been added.
• Latency with large responses has actually been reduced.
• DNSCrypt certificates can now be retrieved over Tor, proxies, and DNS relays.
• Improved server error reporting (thanks to Alison Winters)
• Quite a lot of internal improvements and bug fixes have been made, thanks to Markus Linnala.

2.0.29-beta.1

        Preliminary support for anonymized DNS is here!

2.0.28

• Invalid server entries are now skipped instead of preventing a source from being used. Thanks to Alison Winters for the contribution!
• Truncated responses are immediately retried over TCP instead of waiting for the client to retry. This reduces the latency for large responses.
• Responses sent to the local network are assumed to support at least 1252 bytes packets, and use optional information from EDNS up to 4096 bytes. This also reduces latency.
• Logging improvements: servers are not logged for cached, synthetic and cloaked responses. And the forwarder is logged instead of the regular server for forwarded responses.

 

[Александр Рыжов]

Проверяйте, дайте обратную связь по работоспособности пакета.

[vasek00]

12 минуты назад, Александр Рыжов сказал:

Проверяйте, дайте обратную связь по работоспособности пакета.

СПС

[vasek00]

Пока запустилось, посмотрю что будет, не много конф.подправить.

Скрытый текст

[2019-11-07 16:17:51] [NOTICE] dnscrypt-proxy 2.0.31
[2019-11-07 16:17:51] [NOTICE] Network connectivity detected
[2019-11-07 16:17:51] [NOTICE] Source [public-resolvers.md] loaded
[2019-11-07 16:17:52] [NOTICE] System DNS configuration not usable yet, exceptionally resolving [github.com] using resolver udp[9.9.9.9:53]
[2019-11-07 16:17:56] [NOTICE] System DNS configuration not usable yet, exceptionally resolving [download.dnscrypt.info] using resolver udp[9.9.9.9:53]
[2019-11-07 16:17:59] [NOTICE] Source [relays.md] loaded
[2019-11-07 16:17:59] [NOTICE] Source [quad9-resolvers.md] loaded
[2019-11-07 16:17:59] [NOTICE] Firefox workaround initialized
[2019-11-07 16:17:59] [NOTICE] Now listening to 127.0.0.2:65153 [UDP]
[2019-11-07 16:17:59] [NOTICE] Now listening to 127.0.0.2:65153 [TCP]
[2019-11-07 16:18:00] [NOTICE] [cloudflare] OK (DoH) - rtt: 72ms
[2019-11-07 16:18:00] [WARNING] [adguard-dns] uses a non-standard provider name ('2.dnscrypt.default.ns1.adguard.com.' doesn't start with '2.dnscrypt-cert.')
[2019-11-07 16:18:00] [NOTICE] [adguard-dns] OK (DNSCrypt) - rtt: 121ms
[2019-11-07 16:18:01] [NOTICE] [nextdns] OK (DoH) - rtt: 146ms
[2019-11-07 16:18:01] [NOTICE] [yandex] OK (DNSCrypt) - rtt: 62ms
[2019-11-07 16:18:01] [NOTICE] Sorted latencies:
[2019-11-07 16:18:01] [NOTICE] -    62ms yandex
[2019-11-07 16:18:01] [NOTICE] -    72ms cloudflare
[2019-11-07 16:18:01] [NOTICE] -   121ms adguard-dns
[2019-11-07 16:18:01] [NOTICE] -   146ms nextdns
[2019-11-07 16:18:01] [NOTICE] Server with the lowest initial latency: yandex (rtt: 62ms)
[2019-11-07 16:18:01] [NOTICE] dnscrypt-proxy is ready - live servers: 4

 

 

[vasek00]

Отчет после суточной работы dsncryp-proxy - все работает, по скоростям как было и как стало.

Скрытый текст

[2019-11-07 12:11:42] [NOTICE] dnscrypt-proxy 2.0.27
[2019-11-07 12:11:43] [NOTICE] [adguard-dns] OK (DNSCrypt) - rtt: 65ms
[2019-11-07 12:11:44] [NOTICE] [nextdns] OK (DoH) - rtt: 141ms
[2019-11-07 12:11:45] [NOTICE] [cloudflare] OK (DoH) - rtt: 43ms
[2019-11-07 12:11:45] [NOTICE] [yandex] OK (DNSCrypt) - rtt: 37ms

[2019-11-07 14:11:48] [NOTICE] -    28ms yandex
[2019-11-07 14:11:48] [NOTICE] -    48ms cloudflare
[2019-11-07 14:11:48] [NOTICE] -    65ms adguard-dns
[2019-11-07 14:11:48] [NOTICE] -   150ms nextdns

[2019-11-07 16:11:51] [NOTICE] -    31ms yandex
[2019-11-07 16:11:51] [NOTICE] -    45ms cloudflare
[2019-11-07 16:11:51] [NOTICE] -    61ms adguard-dns
[2019-11-07 16:11:51] [NOTICE] -   145ms nextdns


[2019-11-07 16:20:56] [NOTICE] dnscrypt-proxy 2.0.31
[2019-11-07 16:21:11] [NOTICE] Sorted latencies:
[2019-11-07 16:21:11] [NOTICE] -    45ms cloudflare
[2019-11-07 16:21:11] [NOTICE] -    56ms yandex
[2019-11-07 16:21:11] [NOTICE] -   130ms adguard-dns
[2019-11-07 16:21:11] [NOTICE] -   136ms nextdns

[2019-11-07 20:21:17] [NOTICE] -    47ms cloudflare
[2019-11-07 20:21:17] [NOTICE] -    85ms yandex
[2019-11-07 20:21:17] [NOTICE] -   143ms nextdns
[2019-11-07 20:21:17] [NOTICE] -   149ms adguard-dns

[2019-11-08 06:21:32] [NOTICE] -    50ms cloudflare
[2019-11-08 06:21:32] [NOTICE] -    72ms yandex
[2019-11-08 06:21:32] [NOTICE] -   146ms nextdns
[2019-11-08 06:21:32] [NOTICE] -   149ms adguard-dns

[2019-11-08 12:21:38] [NOTICE] -    47ms cloudflare
[2019-11-08 12:21:38] [NOTICE] -    56ms yandex
[2019-11-08 12:21:38] [NOTICE] -   139ms adguard-dns
[2019-11-08 12:21:38] [NOTICE] -   148ms nextdns

[2019-11-08 13:20:12] [NOTICE] -    38ms google
[2019-11-08 13:20:12] [NOTICE] -    44ms cloudflare
[2019-11-08 13:20:12] [NOTICE] -    57ms yandex
[2019-11-08 13:20:12] [NOTICE] -   148ms adguard-dns

в итоге сейчас стоит

[2019-11-08 13:47:28] [NOTICE] [yandex] OK (DNSCrypt) - rtt: 66ms
[2019-11-08 13:47:29] [NOTICE] [cloudflare] OK (DoH) - rtt: 44ms
[2019-11-08 13:47:30] [NOTICE] [adguard-dns-doh] OK (DoH) - rtt: 114ms
[2019-11-08 13:47:30] [NOTICE] [google] OK (DoH) - rtt: 36ms

 

 

[vasek00]

15 часов назад, valeramalko сказал:

что-то у меня проблемы с dnscrypt, kn-1010 3.3 Beta 1 (может совпало с обновлением OS)

уже несколько раз словил ситуацию, что ЦП уходит в загрузку под 100%, перезапускаю dnscrypt, нагрузка падает на ЦП и все начинает работать

У меня на KN10 - 33B1 все пучком, понаблюдаю.