Update for -resolve changes and use Windows flavor styles

lifenjoiner 2021-01-25 15:42:22 +08:00
parent 33e66be776
commit 6b4cf1f80c

@ -19,6 +19,7 @@ Download dnscrypt-proxy here: [dnscrypt-proxy binaries](https://github.com/jedis
There are quite a few files here, but `dnscrypt-proxy-win64-*.zip` is the one you want.
So, download this file and extract it wherever you want. In can be in your home directory, or wherever you want, really.
For example: `D:\dnscrypt-proxy`.
It is totally possible to have the executable file in one place, the configuration file in another place, the cache files elsewhere and the log files yet somewhere else. But if this is the first time you install the software, and you don't have any good reasons to makes things more complicated than they should be, just keep everything in the same directory. At least to start with, and to ensure that everything works as expected. Then, go crazy if you like. But please don't change everything before even starting the proxy once, and then complain that "it doesn't work". Start with something boring, and gradually tweak it. If you really need to.
@ -26,22 +27,22 @@ Also, do not change your DNS settings at this point.
In the terminal, go to the directory you just extracted using the `cd` command, i.e. something like:
```sh
cd ~\Desktop
```bat
cd /d D:\dnscrypt-proxy
```
The `ls` command should print a bunch of files, among which `dnscrypt-proxy` and `example-dnscrypt-proxy.toml`.
The `dir` command should print a bunch of files, among which `dnscrypt-proxy.exe` and `example-dnscrypt-proxy.toml`.
Create a configuration file based on the example one:
```sh
cp example-dnscrypt-proxy.toml dnscrypt-proxy.toml
```bat
copy example-dnscrypt-proxy.toml dnscrypt-proxy.toml
```
And now, for something intense, go to the dnscrypt-proxy directory, and type:
And now, for something intense, run:
```sh
./dnscrypt-proxy
```bat
dnscrypt-proxy
```
Does it look like it started properly? If not, try to find out why. Here are some hints:
@ -56,16 +57,19 @@ Don't close the terminal window yet. We're going to change the system DNS settin
### Step 3: change the system DNS settings
Open the network settings, and in the TCP/IP panel, remove all existing DNS IP addresses to replace them with: `127.0.0.1`.
Open the network settings, and in the TCP/IP panel, if it's automatically, change it to manually, if it's manually, remove all existing DNS IP addresses (backup first), and then set it to `127.0.0.1`.
Furthermore you will have to add as secondary DNS the one chosen as DNS fallback inside the dnscrypt-proxy.toml configuration file, '9.9.9.9' for the default one, to allow the proxy the choice of DNS servers and the first negotiation of the keys.
Furthermore, you will prefer to add a secondary DNS to allow `dnscrypt-proxy` to use it at startting up to retrieve the initial resolvers. For example the one chosen as DNS fallback inside the dnscrypt-proxy.toml configuration file, '9.9.9.9', or the one you prefer.
Back to the command-line. If dnscrypt-proxy is running, hit `Control` and `C` in the terminal window to stop it.
Back to the command-line. If dnscrypt-proxy is running, hit `Control` and `C` in the terminal window to stop it. And then to launch the server in an extra window, run:
```bat
start dnscrypt-proxy
```
Let's check that everything works by sending a first query using dnscrypt-proxy:
Switch to your previous terminal window. Let's check that everything works by sending a first query using dnscrypt-proxy:
```sh
./dnscrypt-proxy -resolve example.com
```bat
dnscrypt-proxy -resolve example.com
```
Looks like it was successfully able to resolve `example.com`? Sweet! Try a few more things: web browsing, file downloads, use your system normally and see if you can still connect without any DNS-related issues.
@ -76,13 +80,11 @@ If anything ever goes wrong and you want to revert everything, open the network
Hit `Control` and `C` in the `dnscrypt-proxy` terminal window to stop it.
You must still be in the `dnscrypt-proxy` directory at this point.
The `dnscrypt-proxy.toml` file has plenty of options you can tweak. Tweak them if you like. But tweak them one by one, so that if you ever screw up, you will know what exact change made this happen.
The message `bare keys cannot contain '\n'` typically means that there is a syntax error in the configuration file.
Type `./dnscrypt-proxy` to start the server, and `Control`-`C` to stop it. Test, tweak, stop, test, tweak, stop until you are satisfied.
Type `start dnscrypt-proxy` to start the server, and `Control`-`C` to stop it. Test, tweak, stop, test, tweak, stop until you are satisfied.
Are you satisfied? Good, let's jump to step 5!
@ -92,16 +94,16 @@ Hit `Control` and `C` in the `dnscrypt-proxy` terminal window to stop the proxy.
Now, register this as a system service (still with elevated privileges):
```sh
./dnscrypt-proxy -service install
```bat
dnscrypt-proxy -service install
```
If it doesn't spit out any errors, this is great! Your edition of Windows is compatible with the built-in installer.
Now that it's installed, it can be started:
```sh
./dnscrypt-proxy -service start
```bat
dnscrypt-proxy -service start
```
Done!
@ -110,31 +112,31 @@ If it does spit out errors, additional steps for your edition of Windows are req
Want to stop the service?
```sh
./dnscrypt-proxy -service stop
```bat
dnscrypt-proxy -service stop
```
Want to restart the currently running service after a configuration file change?
```sh
./dnscrypt-proxy -service restart
```bat
dnscrypt-proxy -service restart
```
Want to uninstall the service?
```sh
./dnscrypt-proxy -service uninstall
```bat
dnscrypt-proxy -service uninstall
```
Want to check that DNS resolution works?
```sh
./dnscrypt-proxy -resolve example.com
```bat
dnscrypt-proxy -resolve example.com
```
Want to completely delete that thing?
./dnscrypt-proxy -service uninstall & Delete the directory. Done.
`dnscrypt-proxy -service uninstall` & Delete the directory. Done.
## Upgrading