Secure communications between a client and a DNS resolver
License: ISC
Formula JSON API: /api/formula/dnscrypt-proxy.json
Formula code: dnscrypt-proxy.rb
on GitHub
Bottle (binary package) installation support provided for:
Apple Silicon | sequoia | ✅ |
---|---|---|
sonoma | ✅ | |
ventura | ✅ | |
monterey | ✅ | |
Intel | sonoma | ✅ |
ventura | ✅ | |
monterey | ✅ | |
64-bit linux | ✅ |
Current versions:
stable | ✅ | 2.1.5 |
head | ⚡️ | HEAD |
Depends on when building from source:
go | 1.23.3 | Open source programming language to build simple/reliable/efficient software |
After starting dnscrypt-proxy, you will need to point your local DNS server to 127.0.0.1. You can do this by going to System Preferences > "Network" and clicking the "Advanced..." button for your interface. You will see a "DNS" tab where you can click "+" and enter 127.0.0.1 in the "DNS Servers" section. By default, dnscrypt-proxy runs on localhost (127.0.0.1), port 53, balancing traffic across a set of resolvers. If you would like to change these settings, you will have to edit the configuration file: $HOMEBREW_PREFIX/etc/dnscrypt-proxy.toml To check that dnscrypt-proxy is working correctly, open Terminal and enter the following command. Replace en1 with whatever network interface you're using: sudo tcpdump -i en1 -vvv 'port 443' You should see a line in the result that looks like this: resolver.dnscrypt.info |
Analytics:
Installs (30 days) | |
---|---|
dnscrypt-proxy |
134 |
dnscrypt-proxy --HEAD |
1 |
Installs on Request (30 days) | |
dnscrypt-proxy |
134 |
dnscrypt-proxy --HEAD |
1 |
Build Errors (30 days) | |
dnscrypt-proxy |
0 |
Installs (90 days) | |
dnscrypt-proxy |
365 |
dnscrypt-proxy --HEAD |
3 |
Installs on Request (90 days) | |
dnscrypt-proxy |
365 |
dnscrypt-proxy --HEAD |
3 |
Installs (365 days) | |
dnscrypt-proxy |
1,301 |
dnscrypt-proxy --HEAD |
16 |
Installs on Request (365 days) | |
dnscrypt-proxy |
1,300 |
dnscrypt-proxy --HEAD |
16 |