Re:DNSCrypt: A tool for securing communications between a cl...
by dsl on Wednesday June 19, 2013 @12:09PM
(#5906374)
It defaults to OpenDNS because they have been sponsoring development and run the only publicly available DNSCrypt resolvers.
You are free to modify the code for the clients to point to your own server, setup your own server using the proxy code provided, or configure your authoritative DNS servers to talk securely to OpenDNS and protect the entire chain using DNSCurve (which DNSCrypt is based on).
Re:DNSCrypt: A tool for securing communications between a cl...
by simcop2387 on Wednesday June 19, 2013 @02:23PM
(#5907268)
The best i've been able to come up with is using something like dnsmasq plus a public resolver. it'll filter the results for you so that you can have their fake A records get turned into nxdomains. it's not a perfect solution (they can change the a records and you have to reconfigure) but it certainly seems to help.
Re:DNSCrypt: A tool for securing communications between a cl...
by jedisct1 on Wednesday June 19, 2013 @07:23PM
(#5909148)
You don't need dnsmasq for that. dnscrypt ships with the ldns-blocking plugin to block list of domains and IPs: https://github.com/jedisct1/dnscrypt-proxy/blob/master/src/p...
And for the same reason I don't want to use my ISP's DNS. I did a quick websearch for public DNS servers that give honest results without requiring an account, but did not see any mention of encryption compatible with this.