dnscrypt-proxy behind unbound

[Ben.]

Hi,
I tried setting up dnscrypt-proxy behind unbound. Sadly I cant get it to work.

1. I installed the dnscrypt-proxy package.
2. I disabled the OpenDNS service.
3. I started dnscrypt-proxy without any special configuration.
4. I added the following lines to the "Custom Options" field (often referred to as "Advanced Options", but "Advanced" doesnt have a "Options" field):

Code: [Select]

do-not-query-localhost: no
forward-zone:
name: "."
forward-addr: 127.0.0.1@5353
First Unbound said "duplcate forward-zone", so I switched of "Enable Forwarding Mode" which seems to be a conflict.

So basically I had dnscrypt-proxy running on port 5353, unbound on 53. Sadly it seemed unbound didnt forward the requests to dnscrypt-proxy. In the log of dnscrypt I only saw that the server list was downloaded successfully.

Any idea what I could do different or what I should check?
With my setup above it didnt resolve any names. I did also not succeed in providing a port number in the general settings for the DNS servers.

Would be great if you had a hint what I could do/check.

Thanks.

[homenetworkguy]

This response is late to the game, but I thought it may prove useful to anyone that may come across it. I too had a conflict with DNSCrypt-Proxy running on port 5353. I thought that port number sounded familiar when I saw that default value.

It is the port number used by multicast DNS so if you are running the MDNS-Repeater plugin like I am, it will conflict on port 5353. I saw the conflict when I looked at the error log for DNSCrypt-Proxy. I changed the default port number of DNSCrypt-Proxy plugin so it would not conflict and used that port number in the custom config for Unbound.