When using recursive DNS with unbound should we change port 53 of Pihole FTL or Unbound?

The issue I am facing:
Pihole FTL uses port 53
conflicts with port of unbound dns server

Details about my system:
Ubuntu 20.01

What I have changed since installing Pi-hole:

nothing

Please consider working through Pi-hole's guide on setting up unbound, where using port 5335 is suggested.

1 Like

I have but I do not know where is this 8953 port is coming from

tcp    0  0 127.0.0.1:5335    0.0.0.0:*      LISTEN      14540/unbound       
tcp    0  0 127.0.0.1:8953   0.0.0.0:*       LISTEN      14540/unbound       
tcp6  0  0         :::53          :::*       LISTEN      2365/docker-proxy

from unbound.conf manual

control-port: <port number>
    The  port number to listen on for IPv4 or IPv6 control interfaces,
    default is 8953.  If you change this  and  permissions  have  been
    dropped,  you  must  restart  the  server  for  the change to take
    effect.

Unbound control uses that port.

I removed 8953 from control-port but still I am getting 8953 in netstat result.
what other config I should look at ?
UPDATE:
on the other osbox running unbound too has unbound control running with port 8953 but thats not erroring.
only rockpi is having these errors.

Aug 17 19:43:47 rockpi unbound[8785]: [8785:0] error: remote control failed ssl crypto error:1408F09C:SSL routines:ssl3_get_record:http request
Aug 17 19:44:02 rockpi unbound[8785]: [8785:0] error: remote control failed ssl crypto error:1408F09C:SSL routines:ssl3_get_record:http request
Aug 17 19:44:17 rockpi unbound[8785]: [8785:0] error: remote control failed ssl crypto error:1408F09C:SSL routines:ssl3_get_record:http request
Aug 17 19:44:32 rockpi unbound[8785]: [8785:0] error: remote control failed ssl crypto error:1408F09C:SSL routines:ssl3_get_record:http request
Aug 17 19:44:47 rockpi unbound[8785]: [8785:0] error: remote control failed ssl crypto error:1408F09C:SSL routines:ssl3_get_record:http request
Aug 17 19:45:02 rockpi unbound[8785]: [8785:0] error: remote control failed ssl crypto error:1408F09C:SSL routines:ssl3_get_record:http request
Aug 17 19:45:17 rockpi unbound[8785]: [8785:0] error: remote control failed ssl crypto error:1408F09C:SSL routines:ssl3_get_record:http request
Aug 17 19:45:32 rockpi unbound[8785]: [8785:0] error: remote control failed ssl crypto error:1408F09C:SSL routines:ssl3_get_record:http request
Aug 17 19:45:47 rockpi unbound[8785]: [8785:0] error: remote control failed ssl crypto error:1408F09C:SSL routines:ssl3_get_record:http request

As mentioned by mibere and jfb, Port 8953 is used by unbound itself as its standard port for remote controlling it via unbound-control. It would not interfere with normal DNS resolution.

You are likely observing port 8953 in your configuraton because you were trying to reproduce For unbound users: add remote control to your configuration - #4 by vitachaos, and unsuccessfully so, judging by your most recent posts.

Users in this forum are ususally more than willing to help, but you're making that all the more difficult if you spread your problems and configurations over several posts. It's hard to get a complete picture that way.

Also, your original question - what port you should use for unbound when working with Pi-hole - has been answered already.

As it is not necessary to enable remote control in order for unbound to cooperate with Pi-hole, I'd recommend to revert your changes, or better: start from a clean slate.

Following the guide I've posted earlier will lead to a working installation within minutes.

For your issues with remote-controlling unbound, I'd recommend continuing the discussion in the related post, or open a new topic altogether.

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.