AUR (en) - pi-hole-server

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: pi-hole-server 5.18.2-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/pi-hole-server.git (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:	https://github.com/pi-hole/pi-hole
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:	112
Popularity:	2.35
First Submitted:	2016-01-13 12:50 (UTC)
Last Updated:	2024-04-01 18:11 (UTC)

Dependencies (18)

bc (bc-gh^AUR)
bind-tools (bind-development^AUR, bind-git^AUR, bind)
inetutils (inetutils-git^AUR, busybox-coreutils^AUR)
iproute2 (iproute2-git^AUR, busybox-coreutils^AUR, iproute2-selinux^AUR)
jq (jq-git^AUR)
logrotate (logrotate-selinux^AUR, logrotate-git^AUR)
lsof (lsof-git^AUR)
netcat (nmap-netcat^AUR, openbsd-netcat-git^AUR, gnu-netcat-svn^AUR, gnu-netcat, openbsd-netcat)
perl (perl-git^AUR)
pi-hole-ftl^AUR
procps-ng (procps-ng-git^AUR, busybox-coreutils^AUR)
sudo (fake-sudo^AUR, polkit-fakesudo^AUR, sudo-git^AUR, doas-sudo-shim^AUR, doas-sudo-shim-minimal^AUR, sudo-hg^AUR, sudo-selinux^AUR, fudo-git^AUR)
git (git-git^AUR) (make)
lighttpd (optional) – a secure, fast, compliant and very flexible web-server
nginx-mainline (nginx-quic-openssl-hg^AUR, nginx-quic-libressl^AUR) (optional) – lightweight http server
php-cgi (optional) – CGI and FCGI SAPI for PHP needed only for lighttpd
php-fpm (optional) – FastCGI process manager for php needed for nginx
php-sqlite (optional) – sqlite db access for nginx

Required by (2)

padd-git
pi-hole-whitelist-git (optional)

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 (https://wiki.archlinux.org/index.php/Pi-hole) 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 »

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!

max.bra commented on 2024-01-05 09:16 (UTC)

@deemon ok, understood. And yes, pihole-FTL.conf should deserve more love and for next release I can integrate new options that I surely missing over time.

deemon commented on 2024-01-04 20:43 (UTC)

@max.bra naaa it's alright. it's "working as intended" and "didn't crash" apparently. Which is pi-hole-ftl by default allows 1000/60 (1000 queries per minute) from one single host and if this host exceeds the limit, he will be blocked (for how long I don't know, but blocked), while at the same time working for everyone else still normally. https://docs.pi-hole.net/ftldns/configfile/

Now "my problem" was that I have pi-hole-server (and jellyfin server, and some other stuff) running in my desktop computer for all my home LAN (TV's and phones (wifi connected devices etc)), and when I tried to download steam games the desktop computer itself (while being also pi-hole server at the same time) got blocked from DNS requests. So as a cascade effect, anyone else who was using any of the services (also including DNS requests via pi-hole-server) in the LAN got kind of blocked out of it at the same time somehow (although they themselves were not really blocked by pihole?).

Also "my problem #2" was also that there was nothing about this RATE_LIMIT in the /etc/pihole/pihole-FTL.conf file itself (I assumed all the possible options were there, just commented out, which is not the case at all, if you check the link above - there are TONS of other options apparently), which I discovered couple of days later.

Also checked the logs and apparently Steam, while trying to download stuff, does about 1490 DNS queries per minute, which is way over the default pihole limit. So adding the line RATE_LIMIT=1000/10 to the config file, effectively increasing the limit 6x (just in case), fixed the issue currently.

max.bra commented on 2024-01-04 09:45 (UTC)

@deemon or better, are you sure that ftl crash? I manage to understand that... Or simply it cut you out on DNS resolution for a while?