mirrors/dnscrypt-proxy
1
0
Fork 0
mirror of https://github.com/DNSCrypt/dnscrypt-proxy.git synced 2025-03-04 10:24:40 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated Checking (markdown)

szemley 2021-03-25 08:36:50 +00:00
parent 3cb990b16a
commit 80fdcc154b
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Checking.md

@ -51,9 +51,9 @@ sudo tcpdump -n dst port 53 and \
## Verify DNS provider via DNS Leak test
Another thing User can do, to verify if DNSCrypt-Proxy works is to perform simple DNS Leak test. It can be done by using e.g. [dnsleaktest.com](https://www.dnsleaktest.com/) website. Differences between **Standard** and **Extended** tests can be found here: [Standard vs Extended](https://www.dnsleaktest.com/what-is-the-difference.html).
Another thing that User can do, to verify if DNSCrypt-Proxy works correctly, is to perform simple DNS Leak test. It can be done by using e.g. [dnsleaktest.com](https://www.dnsleaktest.com/) website. Differences between **Standard** and **Extended** tests can be found here: [Standard vs Extended](https://www.dnsleaktest.com/what-is-the-difference.html).
Below, there is an example of an extended test, with three servers configured via `server_names` option found in `dnscrypt-proxy.toml` file. Here they are: **meganerd** (DNSCrypt server by MegaNerd.nl, hosted in Amsterdam), **scaleway-fr** (DNSCrypt servers donated by Scaleway.com, maintained by Frank Denis, in Paris) and **dnscrypt.one** (DNSCrypt resolver hosted in Germany, Nuremberg).
Below, there is an example of an extended test, with three servers configured via `server_names` option found in `dnscrypt-proxy.toml` file. Used servers: **meganerd** (DNSCrypt server by MegaNerd.nl, hosted in Amsterdam), **scaleway-fr** (DNSCrypt servers donated by Scaleway.com, maintained by Frank Denis; Paris, France) and **dnscrypt.one** (DNSCrypt resolver hosted in Nuremberg, Germany).
```sh
,-------------------------------------------------------------------------------------------------.
@ -67,6 +67,6 @@ Below, there is an example of an extended test, with three servers configured vi
The output should contain informations about server or servers configured by User (as in above example) or choosed by DNSCrypt-Proxy itself (based on configuration with available filters in `dnscrypt-proxy.toml` file, such as `require_{dnssec,nolog,nofilter}` and `{doh,dnscrypt}_servers` options etc.) As we can see above, everything is okay - the result is compliant with User configuration.
If DNS Leak test shows the configured servers and other methods (see above - "_Block a domain_" or "_Enable query logging_") are working as described and have an expected results, DNSCrypt-Proxy probably runs good. (However, if DNS Leak test shows different IP address/server - e.g. of your **ISP**, it - probably - means, that there is a leak and something is wrong).
If above test shows a proper results and other methods are working as described (see above - "_Block a domain_" or "_Enable query logging_"), then DNSCrypt-Proxy probably works correctly. (However, if DNS Leak test shows a different IP address, e.g. your **ISP**, not the one that has been configured in DNSCrypt-Proxy, it - probably - means, that there is a leak and something is wrong).
**NOTE:** It seems to be a good idea, to redo DNS Leak test, especially after software (e.g. related with networking etc.), system or web browser updates. We cannot be one hundred percent sure, that if today there isn't a DNS Leak, there won't be one tomorrow.