unbound install error? Topic is solved

Have some feedback, questions, suggestions, or just fancy a chat? Pop it in here.
naddel81
Posts: 103
Joined: Sun Jul 21, 2019 12:54 pm

Re: unbound install error?

Post by naddel81 »

pihole shows "127.0.0.1#5353" under DNS. is there a way to really test if unbound is working?

best wishes.
naddel81
Posts: 103
Joined: Sun Jul 21, 2019 12:54 pm

Re: unbound install error?

Post by naddel81 »

journalctl -u unbound outputs

Code: Select all

Jan 11 23:32:38 DietPi systemd[1]: Starting Unbound DNS server...
Jan 11 23:32:38 DietPi package-helper[1458]: /var/lib/unbound/root.key does not exist, copying from /usr/share/dns/root.key
Jan 11 23:32:38 DietPi package-helper[1458]: /var/lib/unbound/root.key has content
Jan 11 23:32:38 DietPi package-helper[1458]: success: the anchor is ok
Jan 11 23:32:38 DietPi unbound[1463]: [1610407958] unbound[1463:0] error: can't bind socket: Address already in use for ::1 port 53
Jan 11 23:32:38 DietPi unbound[1463]: [1610407958] unbound[1463:0] fatal error: could not open ports
Jan 11 23:32:38 DietPi systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Jan 11 23:32:38 DietPi systemd[1]: unbound.service: Failed with result 'exit-code'.
Jan 11 23:32:38 DietPi systemd[1]: Failed to start Unbound DNS server.
Jan 11 23:32:38 DietPi systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Jan 11 23:32:38 DietPi systemd[1]: unbound.service: Scheduled restart job, restart counter is at 1.
Jan 11 23:32:38 DietPi systemd[1]: Stopped Unbound DNS server.
Jan 11 23:32:38 DietPi systemd[1]: Starting Unbound DNS server...
Jan 11 23:32:39 DietPi package-helper[1489]: /var/lib/unbound/root.key has content
Jan 11 23:32:39 DietPi package-helper[1489]: success: the anchor is ok
Jan 11 23:32:40 DietPi unbound[1511]: [1610407960] unbound[1511:0] error: can't bind socket: Address already in use for ::1 port 53
Jan 11 23:32:40 DietPi unbound[1511]: [1610407960] unbound[1511:0] fatal error: could not open ports
Jan 11 23:32:40 DietPi systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Jan 11 23:32:40 DietPi systemd[1]: unbound.service: Failed with result 'exit-code'.
Jan 11 23:32:40 DietPi systemd[1]: Failed to start Unbound DNS server.
Jan 11 23:32:40 DietPi systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Jan 11 23:32:40 DietPi systemd[1]: unbound.service: Scheduled restart job, restart counter is at 2.
Jan 11 23:32:40 DietPi systemd[1]: Stopped Unbound DNS server.
Jan 11 23:32:40 DietPi systemd[1]: Starting Unbound DNS server...
Jan 11 23:32:41 DietPi package-helper[1519]: /var/lib/unbound/root.key has content
Jan 11 23:32:41 DietPi package-helper[1519]: success: the anchor is ok
Jan 11 23:32:41 DietPi unbound[1523]: [1610407961] unbound[1523:0] error: can't bind socket: Address already in use for ::1 port 53
Jan 11 23:32:41 DietPi unbound[1523]: [1610407961] unbound[1523:0] fatal error: could not open ports
Jan 11 23:32:41 DietPi systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Jan 11 23:32:41 DietPi systemd[1]: unbound.service: Failed with result 'exit-code'.
Jan 11 23:32:41 DietPi systemd[1]: Failed to start Unbound DNS server.
Jan 11 23:32:41 DietPi systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Jan 11 23:32:41 DietPi systemd[1]: unbound.service: Scheduled restart job, restart counter is at 3.
Jan 11 23:32:41 DietPi systemd[1]: Stopped Unbound DNS server.
Jan 11 23:32:41 DietPi systemd[1]: Starting Unbound DNS server...
Jan 11 23:32:43 DietPi package-helper[1544]: /var/lib/unbound/root.key has content
Jan 11 23:32:43 DietPi package-helper[1544]: success: the anchor is ok
Jan 11 23:32:43 DietPi unbound[1548]: [1610407963] unbound[1548:0] error: can't bind socket: Address already in use for ::1 port 53
Jan 11 23:32:43 DietPi unbound[1548]: [1610407963] unbound[1548:0] fatal error: could not open ports
Jan 11 23:32:43 DietPi systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Jan 11 23:32:43 DietPi systemd[1]: unbound.service: Failed with result 'exit-code'.
Jan 11 23:32:43 DietPi systemd[1]: Failed to start Unbound DNS server.
Jan 11 23:32:43 DietPi systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Jan 11 23:32:43 DietPi systemd[1]: unbound.service: Scheduled restart job, restart counter is at 4.
Jan 11 23:32:43 DietPi systemd[1]: Stopped Unbound DNS server.
Jan 11 23:32:43 DietPi systemd[1]: Starting Unbound DNS server...
Jan 11 23:32:43 DietPi package-helper[1558]: /var/lib/unbound/root.key has content
Jan 11 23:32:43 DietPi package-helper[1558]: success: the anchor is ok
Jan 11 23:32:44 DietPi unbound[1575]: [1610407964] unbound[1575:0] error: can't bind socket: Address already in use for ::1 port 53
Jan 11 23:32:44 DietPi unbound[1575]: [1610407964] unbound[1575:0] fatal error: could not open ports
Jan 11 23:32:44 DietPi systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Jan 11 23:32:44 DietPi systemd[1]: unbound.service: Failed with result 'exit-code'.
Jan 11 23:32:44 DietPi systemd[1]: Failed to start Unbound DNS server.
Jan 11 23:32:44 DietPi systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Jan 11 23:32:44 DietPi systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Jan 11 23:32:44 DietPi systemd[1]: Stopped Unbound DNS server.
Jan 11 23:32:44 DietPi systemd[1]: Starting Unbound DNS server...
Jan 11 23:32:44 DietPi package-helper[1594]: /var/lib/unbound/root.key has content
User avatar
Joulinar
Posts: 4835
Joined: Sat Nov 16, 2019 12:49 am

Re: unbound install error?

Post by Joulinar »

As already stated twice, do following and restart unbound afterwards

Code: Select all

rm -vf /etc/unbound/unbound.conf.d/{dietpi-pihole,pi-hole}.conf
G_CONFIG_INJECT 'port:[[:blank:]]' '	port: 5353' /etc/unbound/unbound.conf.d/dietpi.conf
G_CONFIG_INJECT 'interface:[[:blank:]]' '	interface: 127.0.0.1' /etc/unbound/unbound.conf.d/dietpi.conf
G_CONFIG_INJECT 'verbosity:[[:blank:]]' '	verbosity: 3' /etc/unbound/unbound.conf.d/dietpi.conf
G_CONFIG_INJECT 'log-queries:[[:blank:]]' '	log-queries: yes' /etc/unbound/unbound.conf.d/dietpi.conf
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
naddel81
Posts: 103
Joined: Sun Jul 21, 2019 12:54 pm

Re: unbound install error?

Post by naddel81 »

already done:

whatsmydnsserver tells me:


Your DNS Server 172.253.1.197
Owner of this server Google LLC
Status of this server Everything is fine
Your DNS Server 172.217.33.193
Owner of this server Google
Status of this server Everything is fine
Click here for more information about your results
User avatar
Joulinar
Posts: 4835
Joined: Sat Nov 16, 2019 12:49 am

Re: unbound install error?

Post by Joulinar »

That's the DNS server of your DietPi device and that's correct. Important is that your network devices at home using pihole
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
naddel81
Posts: 103
Joined: Sun Jul 21, 2019 12:54 pm

Re: unbound install error?

Post by naddel81 »

Image
naddel81
Posts: 103
Joined: Sun Jul 21, 2019 12:54 pm

Re: unbound install error?

Post by naddel81 »

all network devices use pihole since it is the DNS of my router.
User avatar
Joulinar
Posts: 4835
Joined: Sat Nov 16, 2019 12:49 am

Re: unbound install error?

Post by Joulinar »

Unselect Google as upstream DNS server
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
naddel81
Posts: 103
Joined: Sun Jul 21, 2019 12:54 pm

Re: unbound install error?

Post by naddel81 »

done. now my DNS is my own IP:

Your DNS Server 93.214.118.18
Owner of this server Deutsche Telekom AG
Status of this server Everything is fine
User avatar
Joulinar
Posts: 4835
Joined: Sat Nov 16, 2019 12:49 am

Re: unbound install error?

Post by Joulinar »

you can check inside PiHole > QueryLog what is done. On the status you should see which upstream DNS is used
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply