DietPi and Unbound Issues

Creating a bug report/issue

[ :white_check_mark:] I have searched the existing open and closed issues

Required Information

  • DietPi version | cat /boot/dietpi/.version

G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=9
G_DIETPI_VERSION_RC=0
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘applied’
G_LIVE_PATCH_STATUS[1]=‘applied’
G_LIVE_PATCH_STATUS[2]=‘not applicable’
G_LIVE_PATCH_STATUS[3]=‘not applicable’

  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN

bookworm 0

  • Kernel version | uname --all

Linux JuicyPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

  • Architecture | dpkg --print-architecture

arm64

  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)

Pi Zero 2W (AARCH64)

  • Power supply used | (EG: 5V 1A RAVpower)

standard power supply

  • SD card used | (EG: SanDisk ultra)

SanDisk Ultra 64GB

Additional Information (if applicable)

  • Software title | (EG: Nextcloud) PiHole/Unbound
  • Was the software title installed freshly or updated/migrated? All software updated
  • Can this issue be replicated on a fresh installation of DietPi? Trying to solve issue before trying
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID b2b07f9f-efda-4a6b-a91b-fc6ce5af05d2

Steps to reproduce

Installed and setup Pi-hole and Unbound on DietPi. I accidentally installed Apache instead of Lighttpd. I fixed that issue and uninstalled Apache and installed/enabled lighttpd. My ports are not showing correct port numbers.

ss -tulpn | grep LISTEN
tcp   LISTEN 0      5          127.0.0.1:4711      0.0.0.0:*    users:(("pihole-FTL",pid=65220,fd=10))
tcp   LISTEN 0      1024         0.0.0.0:80        0.0.0.0:*    users:(("lighttpd",pid=46410,fd=5))
tcp   LISTEN 0      256        127.0.0.1:5335      0.0.0.0:*    users:(("unbound",pid=65841,fd=4))
tcp   LISTEN 0      1000         0.0.0.0:22        0.0.0.0:*    users:(("dropbear",pid=403,fd=3))
tcp   LISTEN 0      32           0.0.0.0:53        0.0.0.0:*    users:(("pihole-FTL",pid=65220,fd=5))
tcp   LISTEN 0      1024            [::]:80           [::]:*    users:(("lighttpd",pid=46410,fd=4))
tcp   LISTEN 0      1000            [::]:22           [::]:*    users:(("dropbear",pid=403,fd=4))
tcp   LISTEN 0      32              [::]:53           [::]:*    users:(("pihole-FTL",pid=65220,fd=7))

I also cannot access my Verizon router’s network settings website (mynetworksettings.com). I could prior to switching to lighttpd. Pinging and nslookup yields no results/cannot be reached.

Expected behaviour

Pi-Hole should have ports 67, 547, 4711. Based on required ports. Not all hardware has switched to Pi-hole for dns. Unbound doesn’t seem to be working and seems misconfigured.

Actual behaviour

Unbound misconfigured and nslookup yields 127.0.0.1 instead of 192.168.1.194. Pi-hole missing required ports.

Extra details

EDIT: Just tried this:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:4711          0.0.0.0:*               LISTEN      73268/pihole-FTL
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      73406/lighttpd
tcp        0      0 127.0.0.1:5335          0.0.0.0:*               LISTEN      73137/unbound
tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      73268/pihole-FTL
tcp6       0      0 :::80                   :::*                    LISTEN      73406/lighttpd
tcp6       0      0 :::53                   :::*                    LISTEN      73268/pihole-FTL
udp        0      0 127.0.0.1:5335          0.0.0.0:*                           73137/unbound
udp        0      0 0.0.0.0:53              0.0.0.0:*                           73268/pihole-FTL
udp6       0      0 :::53                   :::*                                73268/pihole-FTL

you should see all ports used by PiHole as follow

ss -tulpn | grep pihole

This should show UDP pots 67 and 547 as well. At least if you enabled DHCP server within PiHole.

Port 4711 is already in your list

This is completely correct and is how it should be. Unbound serves as an upstream DNS server for PiHole and is not used by the clients in the local network. Therefore, Unbound only needs to listen to localhost.

Oh okay. So is my configuration correct? I am new to this and followed your dietpi installation. But it’s blocking access to my router’s page even after whitelisting it.

Under network in Pi-hole, only 5 out of 12 show they are using Pi-hole.

And I also get this, does this mean it’s messed up: [quote=“MagicHockeyElf, post:20, topic:75679”]

[1739157921] unbound[71286:0] error: Could not open file: No such file or direct                                                                                                             ory
[1739157921] unbound[71286:0] warning: Continuing with default config settings
[1739157921] unbound[71286:0] error: can't bind socket: Cannot assign requested                                                                                                              address for ::1 port 53
[1739157921] unbound[71286:0] fatal error: could not open ports

[/quote]

pls share the intire log for Unbound.

check PiHole log for related DNS request. There you should see the reason

check the DHCP server settings. Best is to check the clients and which DNS server they have configured.

How do I share the log for Unbound? Sorry I am a total newbie.

journalctl -u unbound. Service

Copy/past output from SSH terminal