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:43:34 +00:00
parent 80fdcc154b
commit 143d3e1b8e
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Checking.md

@ -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 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).
If this 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**, 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.