Open zer0tru5t opened 1 year ago
Use IP instead of the domain for the http_proxy (e.g., https://192.168.1.100:1883/ instead of https://proxy.acme.com:1883/)
I think it is the easy solution and normal way, that leads people without motivation to do it in the hard way.
Platform: macOS Version: 2.1.2
./dnscrypt-proxy -version 2.1.2
./dnscrypt-proxy -check [2022-12-05 13:10:45] [NOTICE] dnscrypt-proxy 2.1.2 [2022-12-05 13:10:45] [NOTICE] Source [public-resolvers] loaded [2022-12-05 13:10:45] [NOTICE] Configuration successfully checked
./dnscrypt-proxy -resolve google.com Resolving [google.com] using 127.0.0.1 port 53
Steps to Reproduce
Configuration
Expected behavior (i.e., solution)
http_proxy domain (e.g., proxy.acme.com) must be resolved using the bootstrap_resolvers.
Other Comments
It works with the following scenarios, so the http_proxy domains are likely not resolved.