search

simonclausen / dnscrypt-autoinstall

Automatic installation and configuration of DNSCrypt (on Debian + Redhat like systems). This script will install DNSCrypt and configure it to start on boot and use an optional dnscrypt service.
Other
224 stars 73 forks source link

Secondary dns server #98

Closed bw4518 closed 6 years ago

bw4518 commented 7 years ago

Hi, how to set secondary dns server?

Because of instability some fallback option is necessary.

elgab commented 7 years ago

Choosing dnscrypt.eu will just work, you should see both resolvers with this: https://www.grc.com/dns/dns.htm

bw4518 commented 7 years ago

Alright I will test that.

Btw, installer fails to get resolvers list: 0curl: (6) Could not resolve host: download.dnscrypt.org Retrieving resolvers failed. Falling back to installed version.

AladW commented 7 years ago

Yes, the dnscrypt.org site is highly unreliable. Again, no real alternatives here due to github not containing any GPG signatures.

On 15.01.2017 17:20, iyx wrote:

Alright I will test that.

Btw, installer fails to get resolvers list: |0curl: (6) Could not resolve host: download.dnscrypt.org Retrieving resolvers failed. Falling back to installed version.|

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/simonclausen/dnscrypt-autoinstall/issues/98#issuecomment-272705383, or mute the thread https://github.com/notifications/unsubscribe-auth/AFQJJDu61KHm3jOKd87Pgl2bltnAWE8Nks5rSkc6gaJpZM4Ldwl5.

simonclausen commented 7 years ago

@AladW, there seems to be a minisig included consistently with the latest releases on Github. Would it be too much to build and use this for verification? Would it even make sense as that then presents the problem of how the minisig source is verified?

AladW commented 7 years ago

Right, the minisign source tarball is signed by another minisig file...

simonclausen commented 6 years ago

Original question was answered and the question on where to get files will probably be handled in #108 in relation to the new status of dnscrypt-proxy.