Package Details: pi-hole-server 4.3.2-7

Git Clone URL: (read-only, click to copy)
Package Base: pi-hole-server
Description: The Pi-hole is an advertising-aware DNS/Web server. Arch adaptation for lan wide DNS server.
Upstream URL:
Keywords: ad block pi-hole
Licenses: EUPL-1.1
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 60
Popularity: 0.57
First Submitted: 2016-01-13 12:50
Last Updated: 2020-02-18 20:03

Pinned Comments

max.bra commented on 2019-10-16 15:28

Since switching to pihole user for pihole-FTL - long term data is not retained on my machine.

sir_randomuser said: For some reason account http has expired, which was the root cause. Seems to be due to a recent systemd change:
Checking /etc/shadow, the user http had a trailing 1:

$ sudo cat /etc/shadow | grep http

Removing the expiration date has resolved it:

$ sudo chage --expiredate -1 http

max.bra commented on 2018-02-09 16:45

ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream.

First of all check if the wiki ( can help then ask here for assistance and tips.
When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.

tdkl commented on 2016-02-15 23:08

You're setting your routers primary DNS to one on internal network? Jeez..

How about you check up on Arch wiki about network configuration first? Because this isn't an issue with this package.

Matty_r commented on 2016-02-09 21:54

It is only unable to ping the router as soon as I change the DNS server on the router to point to the pihole machine.

max.bra commented on 2016-02-09 13:55

with your configuration pihole machine MUST ping your router!!
hardware related?

max.bra commented on 2016-02-09 11:28

pihole machine can ping

Matty_r commented on 2016-02-09 11:24

Yes, that's a typo.

Edit: It doesn't appear to be able to ping, nor my router at However it can ping other computers on the network.

max.bra commented on 2016-02-09 10:29

> ****
> /etc/resolv.conf =
> nameserver <----- this is a typo yes?
> nameserver
> ****

pihole machine can ping

Matty_r commented on 2016-02-09 10:23


Ok, so i'm still having the same issue.

Router was set to pri

/etc/resolv.conf =

Static IP is done through systemd.networkd
/etc/systemd/network/ =



/etc/dnsmasq.conf - was replaced by supplied version
/etc/lighttpd/lighttpd.conf - was replaced by supplied version


# dig
connection timed out; no servers could be reached

# nslookup
connection timed out; no servers could be reached

Matty_r commented on 2016-02-09 07:51


A couple of differences of what I had:
DNS pri - sec

DHCP enabled but was reserved.

It may have been dhcpcd was messing with the config, may need to make sure it's disabled. Give me some time and i'll get back to you with the results. Thanks for your time.

max.bra commented on 2016-02-09 07:43

:: Sure i will say the obvious and you will forgive me for this ::

Static LAN already configured.
DHCP server enabled.
Relevant DHCP options:
Lease -
DNS pri - sec

DHCP client enabled

DHCP client disabled.
Static NIC configuration:
IP addr.
DNS pri - sec

dnsmasq configured via dnsmasq.complete. enabled and started (see configuration)


have we missed something or the problem is more subtle?

edit: typo

Matty_r commented on 2016-02-09 07:25


Router: (DNS relay & DHCP server)

Various other clients are from .1 to .100.

I configured my Router to point to piHole didn't appear to be retrieving DNS entries and then I added to the router as a secondary DNS server. All other clients were able to connect at this point. However piHole still wasn't working.

I connected to piHole and it wasn't able to ping nor, I then attempted to use pacman but it wouldn't connect either. I could however ping