Replies: 17 comments 24 replies
-
|
If you stop the proxy, can you still resolve DNS names?
|
Beta Was this translation helpful? Give feedback.
-
...but of course...this is due -only- to that particular case/example... Resolver : 185.33.111.67 Canonical name: ebay.it. IPv4 addresses: 209.140.136.254, 209.140.139.232, 209.140.136.23 Name servers : dns2.p06.nsone.net., dns3.p06.nsone.net., ns01.ebaydns.com., ns02.ebaydns.com., ns03.ebaydns.com., dns1.p06.nsone.net. HTTPS alias : - Host info : - the resolver is: 185.33.111.67 and really not quad9.net but this is my actual logfile..: [2023-01-15 18:18:45] [NOTICE] dnscrypt-proxy 2.1.2 ...and now...?? |
Beta Was this translation helpful? Give feedback.
-
|
If you stop the proxy, can you still use a web browser to access websites? If so, your system has not been configured to use the proxy. The system DNS must be set to |
Beta Was this translation helpful? Give feedback.
-
|
hi, first thxs for yr attention when i stop the service dnscrypt-proxy, here is the proof: then i'm not able to resolve: N:\DESKTOP\PC\Dns\dnscrypt-proxy>dnscrypt-proxy -resolve ebay.it Unable to resolve: [Timeout] N:\DESKTOP\PC\Dns\dnscrypt-proxy> but i'm still able to use a web browser to access websites: here is the proof:
and i have obviously configurated since the very beginning of my experience with dnscrypt-proxy as per : using primary dns : 127.0.0.1 this is the screenshoot of my settings:
and so...??...where is the bug...?? |
Beta Was this translation helpful? Give feedback.
-
|
...you still are deleting this issue ... |
Beta Was this translation helpful? Give feedback.
-
|
To recap/reproduce:
Is that correct? |
Beta Was this translation helpful? Give feedback.
-
so in your point 4) you write an incorrect thing this is what i've already posted at your close attention in my previous post N:\DESKTOP\PC\Dns\dnscrypt-proxy>dnscrypt-proxy -resolve ebay.it Resolver : 185.33.111.67 Canonical name: ebay.it. IPv4 addresses: 209.140.136.254, 209.140.139.232, 209.140.136.23 Name servers : dns2.p06.nsone.net., dns3.p06.nsone.net., ns01.ebaydns.com., ns02.ebaydns.com., ns03.ebaydns.com., dns1.p06.nsone.net. HTTPS alias : - Host info : - the resolver is: 185.33.111.67 and really not quad9.net but this is my actual logfile..: [2023-01-15 18:18:45] [NOTICE] dnscrypt-proxy 2.1.2 when i stop the service dnscrypt-proxy, here is the proof: then i'm not able to resolve: N:\DESKTOP\PC\Dns\dnscrypt-proxy>dnscrypt-proxy -resolve ebay.it Unable to resolve: [Timeout] N:\DESKTOP\PC\Dns\dnscrypt-proxy> but i'm still able to use a web browser to access websites: here is the proof:
and i have obviously configurated since the very beginning of my experience with dnscrypt-proxy as per : using primary dns : 127.0.0.1 this is the screenshoot of my settings:
so this is a real Bug/Issue and there isn't a truly proof about having DNS traffic encrypted and authenticated how you immagine to solve? cheers |
Beta Was this translation helpful? Give feedback.
-
|
The DNS leak test in your web browser says that you are using Cloudflare, but the next screenshot with your DNS settings show that you configured it to use 9.9.9.9 (Quad9). |
Beta Was this translation helpful? Give feedback.
-
|
simple, i do not imagine to have to explain it to you.... here it is just done for you:
is really time to open a real ISSUE isn't it....???.... |
Beta Was this translation helpful? Give feedback.
-
|
Maybe Quad9 has machines hosted at Namex Consorzio; this is an exchange point after all. Have you tried configuring a different resolver? Do you still see the same resolver IP address being used? |
Beta Was this translation helpful? Give feedback.
-
|
hi, here are my tries: modified config .toml file as: N:\DESKTOP\PC\Dns\dnscrypt-proxy>dnscrypt-proxy -resolve ebay.it Resolver : 172.253.12.197 Canonical name: ebay.it. IPv4 addresses: 209.140.136.254, 209.140.139.232, 209.140.136.23 Name servers : dns1.p06.nsone.net., dns2.p06.nsone.net., dns3.p06.nsone.net., ns01.ebaydns.com., ns02.ebaydns.com., ns03.ebaydns.com. HTTPS alias : - Host info : - then on https://www.dnsleaktest.com/
then i stop the dnscrypt-proxy in services.msc : N:\DESKTOP\PC\Dns\dnscrypt-proxy>dnscrypt-proxy -resolve ebay.it Unable to resolve: [Timeout] but i'm STILL able to surf the web, and not only with firefox where as said i have DoH and Cloudfare so stopping the service -> unable to resolve BUT still able to use web and web browers so a -half issue/Bug - is still there |
Beta Was this translation helpful? Give feedback.
-
|
So everything works as expected! Your queries are going to the proxy, so they are encrypted and authenticated. The confusing part was that the AS name associated with |
Beta Was this translation helpful? Give feedback.
-
|
o no... 👎 you have read only the first part of my reply....please read carefully all my post, then i stop the dnscrypt-proxy in services.msc : N:\DESKTOP\PC\Dns\dnscrypt-proxy>dnscrypt-proxy -resolve ebay.it Unable to resolve: [Timeout] but i'm STILL able to surf the web, and not only with firefox where as said i have DoH and Cloudfare so stopping the service -> unable to resolve BUT still able to use web and web browers so a -half issue/Bug - is still there |
Beta Was this translation helpful? Give feedback.
-
|
Since you configured both |
Beta Was this translation helpful? Give feedback.
-
|
but this is in contrast with what you clearly state: |
Beta Was this translation helpful? Give feedback.
-
|
and more over here it is another clearly proof of the issue: i changed my dns setting changing as:
then try the dnsleaktest:
if what you write was right i should have to find CloudFare 1.1.1.1 cause now this is my new setting, deleted the 9.9.9.9 so a -half issue/Bug - is still there |
Beta Was this translation helpful? Give feedback.
-
|
Used
|
Beta Was this translation helpful? Give feedback.
-
if you should be so very kind NOT to be so cryptic BUT to read carefully my above posts you should at least be able to learn that i have |
Beta Was this translation helpful? Give feedback.
-
Vs
not only ... but also ... Really can't read you. Anyway, I give up on this. |
Beta Was this translation helpful? Give feedback.
-
maybe you do not understand the simple language -written-...if so there is no way to you to simple do a reply..usefull or not...:
|
Beta Was this translation helpful? Give feedback.
-
|
The "Checking that your DNS traffic is encrypted and authenticated" page of the community-written documentation describes 5 different ways to check that the proxy is actually being used by your system. If one of them feels too complicated, try the other ones, they all achieve the same thing. For these tests to be relevant, different resolvers (in your system configuration or browser configuration) that the proxy should not be configured, or else, as configured, they can be used. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
dagli screen che hai fatto lo step 3 non l'hai seguito/letto/capito. p.s. un consiglio, evita di essere arrogante e/o saccente con persone che vogliono aiutarti. di certo non rende tutto più facile, specie se ne hai bisogno. |
Beta Was this translation helpful? Give feedback.
-
maybe you have read Step 3 only now , when it has been modified following my considerations and contributions P.S.: a prayer -read carefully the whole topic- from the very beginning , expecially if you think you should be able to give a a little help |
Beta Was this translation helpful? Give feedback.
-
|
il dns fallback non si mette su windows, ma nel file di configurazione. inoltre vorrei farti notare che non hai letto bene quello che ti ho scritto prima e siccomè ti vedo abbastanza passivo/aggressivo preferisco chiuderla qua. ti auguro un felice 2023 e una buona continuazione di serata |
Beta Was this translation helpful? Give feedback.
-
Step 3 - at the very beginning of this topic - : -now- this misleading part has been removed by the maintainer P.S.: a prayer -read carefully the whole topic- from the very beginning , expecially if you think you should be able to give a a little help |
Beta Was this translation helpful? Give feedback.
-
|
Dear p060477, Thank you for bringing this issue to our attention and for providing the screenshots as evidence. We apologize for any confusion or inconvenience this may have caused. After carefully reviewing the information provided, we have determined that the issue you are experiencing is not a result of a bug. The service is functioning as intended and it appears that you are still able to navigate the web using certain web browsers despite the service being stopped. It is possible that there may have been a misunderstanding about the intended behavior of the service or that the service is designed to only affect certain web browsers. We apologize if this was not clearly communicated. Please let us know if you have any further questions or if there is anything else we can assist you with. We appreciate your feedback and are always looking for ways to improve our service. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
https://github.com/dnscrypt/dnscrypt-proxy/wiki/installation Upgrading Assuming that the official package from this repository was installed, here's how to upgrade to a new version: i really would prefer the reply by https://github.com/jedisct1 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for bringing the confusion in our wiki page to our attention. We apologize for any confusion caused and we appreciate your feedback. Regarding upgrading to a new version of DNSCrypt-proxy, the process will depend on your operating system and the method you used to install the software. In general, you can download the latest version from our releases page (https://github.com/DNSCrypt/dnscrypt-proxy/releases) and replace the old version with the new one. It's always good practice to take a backup of the old version before upgrading. For example, you can keep a copy of your current version in a separate folder, or you can rename the old version to something like "dnscrypt-proxy-2.1.2" before installing the new version. This way, if you encounter any issues with the new version, you can easily revert back to the previous version. Regarding the use of a secondary DNS, it's suggested as a fallback option in case DNSCrypt-proxy is not able to resolve DNS names. This option is usually added to the configuration file of the software and it's set to a public DNS server such as Google's 8.8.8.8 or Cloudflare's 1.1.1.1. The idea behind this option is that if DNSCrypt-proxy is not able to resolve DNS names, the secondary DNS will be used instead, allowing the software to continue working. It should not lead to the issue you described. We apologize for any confusion caused and we will make sure to update our documentation to reflect this. As for the instructions about upgrading, we understand that clear and concise instructions are important for the user experience. We will take note of your feedback and work on providing clearer instructions in the future. Please let us know if you have any further questions or if there is anything else we can assist you with. Thank you for using DNSCrypt-proxy and for bringing this to our attention. We appreciate your continued support and feedback. |
Beta Was this translation helpful? Give feedback.
-
Upgrading the official package from this repository can be a straightforward process, but it's important to take certain precautions to ensure a smooth transition to the new version. First, you should check the change log for any configuration files that need to be updated. This is important because new versions of the software may have different requirements or settings than previous versions. If you're unsure about which configuration files need to be updated, it's a good idea to start over from the example configuration files that are provided with the software. Once you've updated the configuration files, you should check that the new version can properly load the old configuration files. To do this, you can use the command "/path/to/new/dnscrypt-proxy -config /path/to/old/dnscrypt-proxy.toml -check" This command will check that the new version can read the old configuration files and will let you know if there are any issues. Next, you should replace the old dnscrypt-proxy file with the new one. This can typically be done by simply overwriting the old file with the new one. Finally, you should restart the service. This will ensure that the new version of the software is properly loaded and that all of the new settings and configurations are in effect. Please note that, it's always good practice to backup your current config file before making any change and test it in a safe environment before applying it to the production environment. I hope this provides a clear and comprehensive guide for upgrading the official package from this repository. If you have any further questions or concerns, please don't hesitate to reach out. |
Beta Was this translation helpful? Give feedback.
-
Desidero esprimere la mia più sincera gratitudine per le istruzioni fornite. Le vostre indicazioni sono state estremamente utili e precise, e mi hanno permesso di procedere con la procedura di aggiornamento in modo ordinato e senza incontrare alcun tipo di difficoltà. La vostra attenzione ai dettagli e la chiarezza espositiva sono davvero encomiabili. Vi ringrazio ancora una volta per il vostro prezioso contributo e spero di poter continuare a contare sulla vostra preziosa assistenza in futuro. |
Beta Was this translation helpful? Give feedback.
-
|
i make a new discussion about upgrading cause this should turn into a nightmare |
Beta Was this translation helpful? Give feedback.
-
|
I understand that upgrading can sometimes be a difficult process, but please let me know if there is anything specific that is causing issues for you and I will do my best to assist you in resolving them. |
Beta Was this translation helpful? Give feedback.
-
i just started a new discussion here to have a fresh/clear topic |
Beta Was this translation helpful? Give feedback.
-
|
I apologize for misunderstanding your question earlier. I will make sure to reply to your new discussion with easy and simple instructions based on the information provided in the web link you shared. If you have any other specific instructions or questions, please feel free to let me know and I will do my best to help you. Thanks for bringing this to my attention, and please let me know if there's anything else I can do to assist you. |
Beta Was this translation helpful? Give feedback.
-
thank you really so much indeed |
Beta Was this translation helpful? Give feedback.
-
|
You're welcome! I'm glad I could help. I appreciate your kind words and I'm always here to assist you with any question or problem you may have. If you have any other question or concern, don't hesitate to reach out. I'll be happy to help you. Have a great day and cheers! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
hi i want to verify if.
Checking that your DNS traffic is encrypted and authenticated
https://github.com/dnscrypt/dnscrypt-proxy/wiki/Checking
so i set my .toml config file as:
server_names = ['quad9-doh-ip4-port443-filter-pri']
infact the log file shows:
[2023-01-15 11:12:23] [NOTICE] dnscrypt-proxy 2.1.2
[2023-01-15 11:12:24] [NOTICE] Network connectivity detected
[2023-01-15 11:12:24] [NOTICE] Now listening to 127.0.0.1:53 [UDP]
[2023-01-15 11:12:24] [NOTICE] Now listening to 127.0.0.1:53 [TCP]
[2023-01-15 11:12:25] [NOTICE] Source [public-resolvers] loaded
[2023-01-15 11:12:25] [NOTICE] Source [relays] loaded
[2023-01-15 11:12:25] [NOTICE] Firefox workaround initialized
[2023-01-15 11:12:26] [NOTICE] [quad9-doh-ip4-port443-filter-pri] OK (DoH) - rtt: 27ms
[2023-01-15 11:12:26] [NOTICE] Server with the lowest initial latency: quad9-doh-ip4-port443-filter-pri (rtt: 27ms)
[2023-01-15 11:12:26] [NOTICE] dnscrypt-proxy is ready - live servers: 1
but if i start in CLI:
N:\DESKTOP\PC\Dns\dnscrypt-proxy>dnscrypt-proxy -resolve quad9.net
Resolving [quad9.net] using 127.0.0.1 port 53
Resolver : 185.33.111.67
Lying : no
DNSSEC : yes, the resolver supports DNSSEC
ECS : ignored or selective
Canonical name: quad9.net.
IPv4 addresses: 216.21.3.77
IPv6 addresses: 2620:0:871:9000::77
Name servers : ns3.pch.net., ns2.pch.net., anyns.pch.net.
DNSSEC signed : no
Mail servers : 3 mail servers found
HTTPS alias : -
HTTPS info : -
Host info : -
TXT records : v=spf1 a mx ip4:216.21.3.0/24 include:mail.zendesk.com include:servers.mcsv.net include:stspg-customer.com ?all, status-page-domain-verification=0t3fl41mmnjq
i see that the resolver is: 185.33.111.67
so the Namex Consorzio
here it is
https://www.speedguide.net/ip/185.33.111.67
and here it is a more try on the site suggested https://www.dnsleaktest.com/,
with an extended test:
IP Hostname ISP Country
185.33.111.67 None Namex Consorzio Italy
here it is a screenshoot:
the question is: why?
does it means that my DNS traffic is encrypted and authenticated ? yes or no?
and what it means in log file this line ? :
[2023-01-15 11:12:25] [NOTICE] Firefox workaround initialized
thxs so much in adv
cheers
Beta Was this translation helpful? Give feedback.
All reactions