Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#58141 - [dnscrypt-proxy] Dnscrypt does not resolve requests

Attached to Project: Community Packages
Opened by Maxim (mxfm) - Friday, 06 April 2018, 15:00 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 April 2018, 16:27 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Dnscrypt-proxy version 2.0.8-3 (which was updated recently from abandoned v.1) does not listen 53 port and does not process dns requests. It does not work neither as systemd service or as manually started daemon.


Additional info:
* package version(s) 2.0.8-3
* config and/or log files etc.


Steps to reproduce:

systemctl start dnscrypt-proxy

dnscrypt-proxy.socket: Failed to create listening socket: Cannot assign requested address
dnscrypt-proxy.socket: Failed to receive listening socket: Input/output error
dnscrypt-proxy.socket: Failed to listen on sockets: Input/output error
dnscrypt-proxy.socket: Failed with result 'resources'.
Failed to listen on DNSCrypt-proxy socket.
dnscrypt-proxy.service: Job dnscrypt-proxy.service/start failed with result 'dependency'

As another solution try 'dnscrypt-proxy -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml -service start' to launch manually (assuming 127.0.0.1 in resolv.conf). Still, there is no dns response (pinging any domain fails). it does not work probably because dnscrypt still does not listen 53 port (judging by nmap 127.0.0.1).
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 06 April 2018, 16:27 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Configuration problem
Comment by Maxim (mxfm) - Friday, 06 April 2018, 16:20 GMT
Additional information.

After digging up this issue, it appears that the 'second' version changes dnscrypt significantly in terms of options, syntax and the way it is started. Wiki article needs complete revision.

Turns out, that new version expects 'dnscrypt-proxy.toml' configuration file in the same directory or it should be specified with '-config' option. The service can be manually started as '-service start' but it requires prior installation with '-service install'. Dnscrypt tries to install .service file in /etc/systemd/system/ which is not archlinux path. I am not sure, but it appears that '-service start' tries to launch daemon through that .service file and of course this does not work. On the other hand, the package .service file also does not work because it fails to listen to socker for some reason. This package is complete mess.

Loading...