DHCP => DNS server failure

sinjiku · November 8, 2025, 5:57pm

Hello

I have activated DHCP server on Pi-hole and then the dashboard display “DNS Server failed”

In log :

2025-11-08 15:41:49.082 process is missing required capability NET_ADMIN
2025-11-08 15:41:49.083 FAILED to start up

Alpine 3.22.2
Proxmox LXC
One-Step Automated Install
Core version is v6.2.2 (Latest: v6.2.2)
Web version is v6.3 (Latest: v6.3)
FTL version is v6.3.3 (Latest: v6.3.3)

Debug Token:

https://tricorder.pi-hole.net/QWXIDv2J/

What should I do ?

Thanks

rdwebdesign · November 8, 2025, 6:05pm

Pi-hole needs NET_ADMIN capability to run as a DHCP server, but your OS doesn't have this capability enabled.

Please check this similar issue on Github:

github.com/pi-hole/pi-hole

Enabling DHCP server causes DNS server failure

opened 06:07AM - 01 Nov 25 UTC

Sparronator9999

Fixed in next release

### Versions Core version is v6.2.2 (Latest: v6.2.2) Web version is v6.3 (Lates…t: v6.3) FTL version is v6.3.2 (Latest: v6.3.2) ### Platform - OS and version: Alpine Linux v3.22 - Platform: Raspberry Pi 5 ### Expected behavior When enabling the DHCP server on Alpine Linux, upon applying changes, the server should restart successfully and hand out IP addresses. ### Actual behavior / bug Enabling DHCP and applying the new configuration generates this error in the log: ``` Error in dnsmasq configuration: process is missing required capability NET_ADMIN ``` ### Steps to reproduce Steps to reproduce the behavior: 1. Log in to the admin portal. 2. Go to `Settings` > `DHCP`. 3. Tick `DHCP server enabled`, then click `Save and apply`. 4. Upon refreshing, the `Status` indicator changes from `Active` to `DNS server failure`. ## Debug Token - URL: https://tricorder.pi-hole.net/T0mutFAt/ ### Screenshots _If applicable, add screenshots to help explain your problem._ ### Additional context Installed using the one-step automated `bash` script. I did not have this issue on Raspberry Pi OS, which this install of Alpine replaced.

This is a known issue and it will be fixed on the next release.

sinjiku · November 8, 2025, 6:11pm

Thanks for your answer.

I finaly managed to make it work. The container was unprivileged.

Changing it to privileged make the tricks.

I will test to restore it to unprivileged after the next release.

system · November 29, 2025, 6:12pm

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