Open moltar opened 2 years ago
The address 172.24.117.23
was randomly generated by Algo to be used by dnscrypt-proxy
on the VPN server to handle client DNS requests (see local_service_ip
in config.cfg
). SSH to the VPN server and run a command like host google.com 172.24.117.23
to see if DNS resolution is working. If not check:
systemctl status dnscrypt-proxy
Also make sure your client is really connected to the server:
sudo wg
Thanks, @davidemyers!
systemctl status dnscrypt-proxy
Ahh! Found the issue!
systemd
exits with:
Apr 20 11:36:15 algo systemd[1]: Started DNSCrypt client proxy.
Apr 20 11:36:15 algo dnscrypt-proxy[3190]: [2022-04-20 11:36:15] [FATAL] Near line 549 (last key parsed 'static.NextDNS-xyz'): expected a top-level item to end with a newline, comment, or EOF, but got '[' instead
Apr 20 11:36:15 algo systemd[1]: dnscrypt-proxy.service: Main process exited, code=exited, status=255/EXCEPTION
Apr 20 11:36:15 algo systemd[1]: dnscrypt-proxy.service: Failed with result 'exit-code'.
Because the /etc/dnscrypt-proxy/dnscrypt-proxy.toml
config file gets generated as:
## ... snip
[static]
[static.'NextDNS-abc']
stamp = 'sdns://xyz' [static.'NextDNS-ipv6-abc']
stamp = 'sdns://xyz'
# [static.'myserver']
# stamp = 'sdns:AQcAAAAAAAAAAAAQMi5kbnNjcnlwdC1jZXJ0Lg'
Note the missing line break before ipv6 config.
Probably need to remove the -
here?
Probably need to remove the
-
here?
I think you might be right about that.
Describe the bug
I'm running algo from inside a Docker container.
When the setup finishes, I get the files created:
When I try to connect to this configuration, the connect works, but DNS resolution does not work.
Because
172.24.117.23
, I think, is internal Docker DNS.Why is this set to this IP?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I am not sure what the correct behaviour should be. I realize that the script has no way of knowing host's IP.
But setting I'm not sure if setting it to the host's IP is also the correct option? What if I want to use this config somewhere else?
Additional context
N/A
Full log