Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: pi-hole-server 5.18.3-4

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:	0.134716
First Submitted:	2016-01-13 12:50 (UTC)
Last Updated:	2024-08-10 12:32 (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-git^AUR, logrotate-selinux^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, git-gl^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

« First ‹ Previous 1 .. 74 75 76 77 78 79 80 81 82 Next › Last »

tdkl commented on 2016-02-16 20:07 (UTC)

@max.bra: do you also have 0 dns queries and 0 traffic % displayed after the 2.5.2 update in the Pi-hole admin website ? Seems they played with the chronometer.sh a bit : https://github.com/pi-hole/pi-hole/commit/7116634739285197003dc01d02d76217d02418b3

tdkl commented on 2016-02-15 23:08 (UTC)

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 (UTC)

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 (UTC)

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

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

pihole machine can ping 8.8.8.8?

Matty_r commented on 2016-02-09 11:24 (UTC) (edited on 2016-02-09 11:31 (UTC) by Matty_r)

Yes, that's a typo. Edit: It doesn't appear to be able to ping 8.8.8.8, nor my router at 10.0.0.138. However it can ping other computers on the network.

max.bra commented on 2016-02-09 10:29 (UTC) (edited on 2016-02-09 10:32 (UTC) by max.bra)

> **** > /etc/resolv.conf = > nameserver 120.0.0.1 <----- this is a typo yes? > nameserver 10.0.0.138 > **** pihole machine can ping 8.8.8.8?

Matty_r commented on 2016-02-09 10:23 (UTC)

@max.bra: Ok, so i'm still having the same issue. Router was set to pri 10.0.0.12 **** /etc/resolv.conf = nameserver 120.0.0.1 nameserver 10.0.0.138 **** Static IP is done through systemd.networkd **** /etc/systemd/network/eth0.network = [Network] DHCP=no DNS=127.0.0.1 DNS=10.0.0.138 [Address] Address=10.0.0.12/24 [Route] Gateway=10.0.0.138 ******** /etc/dnsmasq.conf - was replaced by supplied version /etc/lighttpd/lighttpd.conf - was replaced by supplied version troubleshooting # dig google.com connection timed out; no servers could be reached # nslookup google.com connection timed out; no servers could be reached

Matty_r commented on 2016-02-09 07:51 (UTC)

@max.bra: A couple of differences of what I had: Router: DNS pri 10.0.0.12 - sec 8.8.8.8 piHole: DHCP enabled but 10.0.0.12 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 (UTC) (edited on 2016-02-09 07:44 (UTC) by max.bra)

:: Sure i will say the obvious and you will forgive me for this :: Router: 10.0.0.138 Static LAN already configured. DHCP server enabled. Relevant DHCP options: Lease 10.0.0.1 - 10.0.0.100 DNS pri 10.0.0.12 - sec 10.0.0.138 Clients: DHCP client enabled Pi-Hole: DHCP client disabled. Static NIC configuration: IP addr. 10.0.0.12 DNS pri 127.0.0.1 - sec 10.0.0.138 dnsmasq configured via dnsmasq.complete. enabled and started (see configuration) ---- have we missed something or the problem is more subtle? edit: typo

« First ‹ Previous 1 .. 74 75 76 77 78 79 80 81 82 Next › Last »