Package Details: pi-hole-server 5.18.2-1

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.2
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 111
Popularity: 0.74
First Submitted: 2016-01-13 12:50 (UTC)
Last Updated: 2024-04-01 18:11 (UTC)

Dependencies (18)

Required by (2)

Sources (15)

Pinned Comments

max.bra commented on 2018-02-09 16:45 (UTC) (edited on 2019-10-18 23:14 (UTC) by max.bra)

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.

Latest Comments

1 2 3 4 5 6 .. 80 Next › Last »

max.bra commented on 2024-05-10 20:34 (UTC)

@munir0b0t hi and thanks for reporting, anyway. pihole packages have nearly 10 years of testing and building experience. how can it be possible to forget a dependency like 'patch'?

munir0b0t commented on 2024-05-10 20:16 (UTC)

Please add patch a build dependency of the package. It's not installed as a dependency of git, and the build fails without it.

trainzkid commented on 2024-04-30 05:06 (UTC)

Is there a way to force pihole to reread the /etc/pihole/setupVars.conf file? I just had an issue where after an update and reboot, my network interface names changed, so I had to change that file to match my current interfaces, but reloading/restarting pihole-FTL (via systemctl reload/restart pihole-FTL) didn't cause pihole to start listening on the correct interface, only localhost. I found the line in the dnsmasq conf file (located at /etc/dnsmasq.conf.d/01-pihole.conf), but it was still set to the previous interface. I was able to manually comment it out and restart pihole to fix the issue, but...?? that conf file clearly says not to update it manually.

I saw online from old forum posts that pihole -r or pihole reconfigure would do this, but the Arch version doesn't seem to support that flag, though that could just be because it's an old deprecated flag or something.

trainzkid commented on 2024-04-06 03:54 (UTC)

@kikislater I believe the reason for rate limiting is to help protect against DDOS/Denial of Service attacks. If you're only accessing pihole from your LAN, you're probably fine

kikislater commented on 2024-04-06 02:46 (UTC) (edited on 2024-04-06 02:48 (UTC) by kikislater)

@trainzkid: I have disabled rate limiting as well from settings > DNS > rate-limiting (put 0). As I do a lot with ogc API queries on local network then use this same kind of requests over internet, it's annoying to have a device blocked due to number of queries

trainzkid commented on 2024-04-05 23:05 (UTC)

Can confirm with @deemon, steam does do an insane amount of DNS queries, I've had steam cause my desktop to get blocked from pihole DNS quite a few times before. I've never had it block others though, only my desktop, so I never really think too much of it and it fixes itself after a little while. Definitely not great but not pihole's fault.

I have wondered how to set up some sort of caching for steam at the server side, just haven't figured out how yet.

ShamanSTK commented on 2024-04-03 00:19 (UTC)

Can confirm deleting the the ~/.cache/yay folder fixes NoIdea's issue.

max.bra commented on 2024-04-02 18:23 (UTC)

hi NoIdea, seems to be everything ok here. please try to clear your AUR helper cache and give a try.

NoIdea commented on 2024-04-02 18:15 (UTC)

getting the below when trying to upgrade to 5.18.2-1, does PKGBUILD need to be corrected?

ERROR: One or more files did not pass the validity check!