Unbound - (How have I managed this ?)

I moved from 32-64 bit Dietpi and I cant get Unbound working properly

Somehow I’m getting this

unbound-checkconf[1117:0] fatal error: interface: present twice, cannot bind same ports twice.

Previously had unbound working without issue.

Difference being that up until now I’ve always used the guide at https://docs.pi-hole.net/guides/dns/unbound/

Upon reinstalliung Dietpi I realised there was an autoinstaller so used that… (no prior installation)

Is it fixable or would I be easier just nuking unbound from dietpi (uninstall) and start again ?

Edit;- Uninstall/reinstall fixed issue. I THINK it was because I’d tried to install concurrently with Pihole… set pihole up first and it is fine. I also didn’t have “apt-utils” installed as a dependency - that delayed the install so it didn’t work properly… plus I may have also ran installer twice :roll_eyes:

Yeah my fault. I can delete this if you like… :smiley:


currently there is an bug on our install script if you install PiHole as well as unbound same time. But nothing that can’t be fixed

can you share ls -la /etc/unbound/unbound.conf.d/

root@DietPihole:~# ls -la /etc/unbound/unbound.conf.d/
total 20
drwxr-xr-x 2 root root 4096 Apr 25 01:57 .
drwxr-xr-x 3 root root 4096 Apr 25 01:26 ..
-rw-r--r-- 1 root root 3525 Apr 25 01:57 dietpi.conf
-rw-r--r-- 1 root root  302 May 25  2020 qname-minimisation.conf
-rw-r--r-- 1 root root  190 May 25  2020 root-auto-trust-anchor-file.conf

Sorry only just saw the request. :cry:

However I’ve ran into other issues which I’ll post once I’ve had some sleep .

Now on 7.1 Beta all seems to be working ok. (will explain)

PS Didn’t they Update Unbound in one of the APT updates recently… I remember getting 1.1.13 in one of the APT updates last week but it is back at 1.9.0 again … (I see 1.1.3-1 is in the debian testing branch)

The issue with unbound has been fixed in current DietPi release 7.0.2 already.

Unbound version on Debian Buster is 1.9 still. Version 1.13 is available on Bullseye.