Something along the lines of "When forwarding queries with [[Unbound]], ''dnscrypt-proxy'' should be started through {{ic|dnscrypt-proxy.socket}}" in the [[DNSCrypt#Startup]] section. As it is now, the {{ic|dnscrypt-proxy.toml}} file contains {{ic|<nowiki>listen_addresses = ['127.0.0.1:53', '[::1]:53']</nowiki>}} so for an average user following [[DNSCrypt#Unbound]] (especially when coming directly from the [[Unbound]] page) this would lead to a misconfiguration. -- [[User:Wincraft71|Wincraft71]] ([[User talk:Wincraft71|talk]]) 15:34, 28 May 2018 (UTC)

Something along the lines of "When forwarding queries with [[Unbound]], ''dnscrypt-proxy'' should be started through {{ic|dnscrypt-proxy.socket}}" in the [[DNSCrypt#Startup]] section. As it is now, the {{ic|dnscrypt-proxy.toml}} file contains {{ic|<nowiki>listen_addresses = ['127.0.0.1:53', '[::1]:53']</nowiki>}} so for an average user following [[DNSCrypt#Unbound]] (especially when coming directly from the [[Unbound]] page) this would lead to a misconfiguration. -- [[User:Wincraft71|Wincraft71]] ([[User talk:Wincraft71|talk]]) 15:34, 28 May 2018 (UTC)

+

+

:You need to 1. configure [[unbound]], and 2. configure [[DNSCrypt]], so you should read both pages (from the start). Why is that not clear? -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 20:11, 28 May 2018 (UTC)

Revise or remove?

No matter how well it's written, this basically does what the instanced services method does, but users make the individual socket and service files by hand. Even if individual resolvers need different configurations, that could be achieved by overriding the instanced services. Some of this I would recycle into the instanced services section (Tip, Lastly). quequotion (talk) 16:04, 25 January 2017 (UTC)

Draft

Redundant DNSCrypt providers

To use additional dnscrypt providers, copy /usr/lib/systemd/system/dnscrypt-proxy.service to a new file, /etc/systemd/system/dnscrypt-proxy-short-name.here.service and specify a different resolver using the -R flag with a short name from dnscrypt-resolvers.csv.

Tip: Any other options you wish to use with this resolver should be specified on this command line; the use of a config file with command line options is unsupported.

Then copy /usr/lib/systemd/system/dnscrypt-proxy.socket to a new file, /etc/systemd/system/dnscrypt-proxy-short-name.here.socket and, specify another port.

Comment: This is a cheapened version of the multiple instances method; considering to delete the above and move the below under "Create instanced systemd service". quequotion (talk) 02:46, 26 March 2017 (UTC)

Lastly, update your local DNS cache program to point to new service's port. For example, with unbound the configuration file would look like if using ports 5353 for the original socket and 5354 for the new socket.

Comment: command-line options override the configuration file (when run as a systemd service at least) quequotion (talk) 15:29, 24 January 2017 (UTC)

Comment: If this is the case, it is a bug - the man page says OPTIONS (ignored when a configuration file is provided). -- Lahwaacz (talk) 13:18, 24 January 2017 (UTC)

Comment: That's bad news; this is definetly the case. So users who want redundant / instanced services need to specify all their options on the command line and that's fine with me. quequotion (talk) 13:34, 24 January 2017 (UTC)

Comment: Or simply have multiple config files and an instantiated service similar to this one to select the right config. -- Lahwaacz (talk) 13:45, 24 January 2017 (UTC)

Comment: Sounds good; putting this back into the proposal with some adjustments. quequotion (talk) 14:15, 24 January 2017 (UTC)

Comment: The more I boil down the method above, the more it seems like it would be more sensible to remove it from the page entirely and just recommend the instances method. quequotion (talk) 15:07, 24 January 2017 (UTC)

Backup DNSCrypt resolver - especially with the new configuration file

Usually when setting a dns resolver you will always have the option to set a second/backup dns resolver (android,windows,networkmanager,router, what ever).

I think the wiki should cover a way on how to achieve the same with dnscrypt. Especially as some if the dnscrypt resolvers like to go offline every now and then (looking at you dnscrypt.eu-nl).

I have a running setup (which caused me some struggles to achieve that setup) but I have no idea how to replicate it. Espcially with the new configuration file which seems like it will only cover one dnscrypt instance?

Right now I have 2x dnscrypt running in systemd and the resolver.conf will choose which ever is online/working.

But this is with the old configuration file, not the new one? Also it seems like this only covers unbound but what about e.g. dnsmasq? —This unsigned comment is by Utini2000 (talk) 16:21, 30 December 2016. Please sign your posts with ~~~~!

I'm sorry, i explained my intention to merge these articles. I invited people to read my article to revist it, if is necessary, before completing the merging. "Users are encouraged to participate in merger discussions or simply complete the merge". Can i do the merging?

Yes you can update DNSCrypt but be sure to do it gradually with edit summaries explaining your changes. --Larivact (talk) 12:19, 14 May 2018 (UTC)

I've updated Dnscrypt enough to where your second article is unnecessary. I don't understand why your configuration instructions say to edit in static servers, however. The user would be better off leaving the default public resolvers under [sources], and choosing their requirements with the require_dnssec, require_nolog, require_nofilter options. Or use server_names to choose a server from the [sources]. -- Wincraft71 (talk) 22:15, 15 May 2018 (UTC)

"CapabilityBoundingSet" in /* Sandboxing */

With the newest update using the "CapabilityBoundingSet=CAP_IPC_LOCK CAP_SETGID CAP_SETUID" option causes this error:

That has nothing with the "newest update" (whatever that means today), AmbientCapabilities=CAP_NET_BIND_SERVICE appeared in [3]. -- Lahwaacz (talk) 21:47, 27 May 2018 (UTC)

Well the only way I can get it to work when starting directly or from the socket dnscrypt-proxy.socket is by adding CAP_NET_BIND_SERVICE to the end of CapabilityBoundingSet=. I meant "the update from 9 days ago". It has to do with an update that happened recently is what I mean. -- Wincraft71 (talk) 22:21, 27 May 2018 (UTC)

Startup method when using Unbound

It should be specified clearly that Unbound uses the socket method with empty listen_addresses from the DNSCrypt#Startup section and upstream [4].

Something along the lines of "When forwarding queries with Unbound, dnscrypt-proxy should be started through dnscrypt-proxy.socket" in the DNSCrypt#Startup section. As it is now, the dnscrypt-proxy.toml file contains listen_addresses = ['127.0.0.1:53', '[::1]:53'] so for an average user following DNSCrypt#Unbound (especially when coming directly from the Unbound page) this would lead to a misconfiguration. -- Wincraft71 (talk) 15:34, 28 May 2018 (UTC)

You need to 1. configure unbound, and 2. configure DNSCrypt, so you should read both pages (from the start). Why is that not clear? -- Lahwaacz (talk) 20:11, 28 May 2018 (UTC)