A culpa da análise SystemD mostra 21s.
A questão parece estar aqui:
sudo systemctl status dnscrypt-proxy
Sep 30 22:18:22 HorniSlezsko systemd[1]: Listening on dnscrypt-proxy listening socket.
Sep 30 22:18:24 HorniSlezsko dnscrypt-proxy[1036]: [INFO] + DNS Security Extensions are supported
Sep 30 22:18:24 HorniSlezsko dnscrypt-proxy[1036]: [INFO] + Namecoin domains can be resolved
Sep 30 22:18:24 HorniSlezsko dnscrypt-proxy[1036]: [INFO] + Provider supposedly doesn't keep logs
Sep 30 22:18:24 HorniSlezsko dnscrypt-proxy[1036]: [NOTICE] Starting dnscrypt-proxy 1.6.1
Sep 30 22:18:24 HorniSlezsko dnscrypt-proxy[1036]: [INFO] Generating a new session key pair
Sep 30 22:18:24 HorniSlezsko dnscrypt-proxy[1036]: [INFO] Done
Sep 30 22:18:39 HorniSlezsko dnscrypt-proxy[1036]: [ERROR] Unable to retrieve server certificates
Sep 30 22:18:40 HorniSlezsko dnscrypt-proxy[1036]: [INFO] Refetching server certificates
Sep 30 22:18:45 HorniSlezsko dnscrypt-proxy[1036]: [INFO] Server certificate #808464433 received
Ele nunca pode se conectar no começo e sempre é feito com sucesso 15s depois.
A única alteração que fiz foi em /lib/systemd/system/dnscrypt-proxy.service , nesta linha:
ExecStart=/usr/sbin/dnscrypt-proxy \
--resolver-name=soltysiak
Eu tentei vários resolvedores e o mesmo problema.