dnscrypt-proxy
Secure communications between a client and a DNS resolver
/api/formula/dnscrypt-proxy.json (JSON API)
Formula code on GitHub
Current versions:
| stable | ✅ | 2.0.44 |
| head | ⚡️ | HEAD |
| bottle | 🍾 | catalina, mojave, high_sierra |
Depends on when building from source:
| go | 1.14.4 | 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: $(brew --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 |
870 |
dnscrypt-proxy --HEAD |
1 |
| Installs on Request (30 days) | |
dnscrypt-proxy |
833 |
dnscrypt-proxy --HEAD |
1 |
| Build Errors (30 days) | |
dnscrypt-proxy |
0 |
| Installs (90 days) | |
dnscrypt-proxy |
1,719 |
dnscrypt-proxy --HEAD |
10 |
dnscrypt-proxy --devel |
8 |
| Installs on Request (90 days) | |
dnscrypt-proxy |
1,645 |
dnscrypt-proxy --HEAD |
10 |
dnscrypt-proxy --devel |
8 |
| Installs (365 days) | |
dnscrypt-proxy |
11,266 |
dnscrypt-proxy --HEAD |
18 |
dnscrypt-proxy --devel |
8 |
| Installs on Request (365 days) | |
dnscrypt-proxy |
10,672 |
dnscrypt-proxy --HEAD |
18 |
dnscrypt-proxy --devel |
8 |
