Sounds good to me. Looking forward to the next beta. Current installer works like a charm, btw. Thanks!
One remark on the current (beta12) installer, not sure wether on purpose, but nevertheless it might be worth mentioning. During executing the installer you ask for an initial DNS-server, quad9 by default, whichs gets added to dnsmasq.conf. However, if the user specifies a different dns server, it's not being added to dnscrypt-proxy.toml as fallback:
Code:
## Fallback resolver
## This is a normal, non-encrypted DNS resolver, that will be only used
## for one-shot queries when retrieving the initial resolvers list, and
## only if the system DNS configuration doesn't work.
## No user application queries will ever be leaked through this resolver,
## and it will not be used after IP addresses of resolvers URLs have been found.
## It will never be used if lists have already been cached, and if stamps
## don't include host names without IP addresses.
## It will not be used if the configured system DNS works.
## A resolver supporting DNSSEC is recommended. This may become mandatory.
fallback_resolver = "9.9.9.9:53"
Not sure you've done that on purpose?
I also have a feature request to consider for when it's stable: Would you consider building in an option to check during install wether there's an existing config file and ask the user if it wants to keep using the existing config or start fresg? Maybe it's possible to skip several questions and copy the values from, let's say
dnscrypt-proxy.toml.old, to the new config file and only ask user input on new variables/functionality (if any). An option to reconfigure afterwards could be used to start completely fresh with the default. It's not mandator by far, would be nice-to-have and might be more convenient to a broader public.
@Protik, the functionality you are looking for is already included in dnscrypt-proxy v2 since a few betas ago. Just edit /jffs/dnscrypt-proxy/dnscrypt-proxy.toml and remove the hash before the line
file = 'query.log' as shown below and a file will be created in the same directory where the executable is. You can also specify a full path if you want to store it elsewhere, for example to have the file deleted on reboot. If you wish to keep logging dns queries, I suggest you do this on usb instead of jffs, by specifying an absolute path to /tmp/mnt/<your_usb>/<folder_name>/query.log. A restart of dnscrypt-proxy or rebooting your router is required for these changed settings to take effect.
Code:
###############################
# Query logging #
###############################
## Log client queries to a file
[query_log]
## Path to the query log file (absolute, or relative to the same directory as the executable file)
file = 'query.log'
My assumption was as it is mentioned in the toml file, it would work out of the box. But apparently not.
Just tested it, it does. Tested it before, it worked then, but maybe it got broken in between betas. In beta 12 it works as supposed to, I'm looking at it now (see attached file).
