ssl upstream config?

Hi all,

I am trying to use Unbound’s SSL upstream. Cause I am new to Unbound here, I doubt I might configure them wrong. Both sides use unbound1.5.7

The configuration of Resolver:

server:

directory: “/etc/unbound”

username: root

make sure unbound can access entropy from inside the chroot.

e.g. on linux the use these commands (on BSD, devfs(8) is used):

mount --bind -n /dev/random /etc/unbound/dev/random

and mount --bind -n /dev/log /etc/unbound/dev/log

chroot: “/etc/unbound”

logfile: “/etc/unbound/unbound.log” #uncomment to use logfile.

pidfile: “/etc/unbound/unbound.pid”

verbosity: 1 # uncomment and increase to get more logging.

listen on all interfaces, answer queries from the local subnet.

interface: 0.0.0.0

interface: ::0

access-control: 10.0.0.0/8 allow

The configuration of Forwarder:

unbound.conf(5) config file for unbound(8).

server:

directory: “/etc/unbound”

username: root

make sure unbound can access entropy from inside the chroot.

e.g. on linux the use these commands (on BSD, devfs(8) is used):

mount --bind -n /dev/random /etc/unbound/dev/random

and mount --bind -n /dev/log /etc/unbound/dev/log

chroot: “/etc/unbound”

logfile: “/etc/unbound/unbound.log” #uncomment to use logfile.

pidfile: “/etc/unbound/unbound.pid”

verbosity: 1 # uncomment and increase to get more logging.

listen on all interfaces, answer queries from the local subnet.

interface: 0.0.0.0

interface: ::0

access-control: 10.0.0.0/8 allow

tcp-upstream: yes

ssl-upstream: yes

ssl-port: 853

forward-zone:

name: “.”

forward-addr: 10.4.1.2@853

server:

ssl-upstream: yes

tcp-upstream: yes

do-daemonize: no

logfile: “”

verbosity: 10

Any help is welcome. Thanks.

Hi RunxiaWan,

The 'Resolver' that you configured does not send traffic to the
Forwarder, and this machine does not provide service on port 853 with
SSL to clients. I am not sure if it should send traffic elsewhere in
your design, but it is acting as a full resolver to the authority server
s.

The 'Forwarder' that you configured, is sending traffic to another
address, and it sends it over port 853 with SSL upstream. It also
does not provide service on port 853 with SSL to clients.

Since neither of them is providing service on port 853 (with an
interface: line that has @853 on it) and ssl-port set to 853, perhaps
your design does not have a server that provides SSL service to
clients. Such a server should also configure ssl-service-key and
ssl-service-pem files with the certificate for the SSL service.

Best regards, Wouter