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.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.49
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 .. 49 50 51 52 53 54 55 56 57 58 59 .. 82 Next › Last »

SilverMight commented on 2018-08-21 04:06 (UTC)

don't mean to come off as impatient but any chance for 4.0 soon?

phixion commented on 2018-08-16 23:51 (UTC)

I see how it is! Enjoy your vacation.

max.bra commented on 2018-08-16 13:58 (UTC)

I was hoping to work on the packages from the beach but the WiFi is out of order... :-D

phixion commented on 2018-08-16 06:29 (UTC)

any chance to see this pushed to 4.0 anytime soon?

josealberto4444 commented on 2018-08-07 09:43 (UTC) (edited on 2018-08-07 10:50 (UTC) by josealberto4444)

Hi, tsago,

No, I get same error, it doesn't matter what I ask to dig:

$ dig +short www.example.com @127.0.0.1
dig: parse of /etc/resolv.conf failed
$ dig +short www.lkjasdfbo.buvoqwuyd @300.300.330.3331
dig: parse of /etc/resolv.conf failed

The thing is that it can actually resolve names, as I can ping anywhere:

$ ping gnu.org
PING gnu.org (208.118.235.148) 56(84) bytes of data.
64 bytes from wildebeest.gnu.org (208.118.235.148): icmp_seq=1 ...

I'll ask in generic forums, thanks.

tsago commented on 2018-08-06 15:14 (UTC)

Hi, josealberto4444,

This looks more like a generic DNS issue, not really pi-hole related. Generic forums might be a better place for this.

But anyway, can you resolve something when you ask dnsmasq? E.g.: dig +short www.example.com @127.0.0.1 (or @192.168.1.153)

josealberto4444 commented on 2018-08-06 14:55 (UTC) (edited on 2018-08-06 15:00 (UTC) by josealberto4444)

Hi, I have a problem with resolving DNS requests from the machine that is actually running pi-hole as a server. I get this when trying to update lists:

$ pihole -g
[✗] DNS resolution is currently unavailable

Also, I think this is related, when using dig to find my external IP address:

$ dig +short myip.opendns.com @resolver1.opendns.com        
dig: parse of /etc/resolv.conf failed

I looked for a solution in the pi-hole forums, but the most related thing was this one:
https://discourse.pi-hole.net/t/dns-resolution-is-currently-unavailable/5797
which links to these:
https://github.com/pi-hole/pi-hole/issues/1800
https://github.com/pi-hole/pi-hole/issues/1806
but all that was solved in v3.3 in theory.

Just in case, my /etc/resolv.conf:

$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 192.168.1.153
nameserver 192.168.1.1
nameserver fe80::1%2

IP 192.168.1.153 is the machine running pi-hole (Raspberry Pi 3B+).

Thanks!

max.bra commented on 2018-07-16 10:01 (UTC)

@butterymales:

Exactly: this is not a normal pihole installation.

ASAP I will sed out that line. Thanks for reporting.

uint2048_t commented on 2018-07-16 04:21 (UTC) (edited on 2018-07-16 04:23 (UTC) by uint2048_t)

I've been noticing this line spamming the syslog every so often:

 Jul 15 18:29:27 zserve lighttpd-angel[9694]: sh: line 0: cd: /etc/.pihole/: No such file or directory

It looks like it's from line 204 in /srv/http/pihole/pihole/index.php

 $phVersion = exec("cd /etc/.pihole/ && git describe --long --tags");

On a 'normal' pihole install that directory would exist. Is it worth it to populate that variable with the pihole git version?

Taijian commented on 2018-07-12 11:25 (UTC)

OK, I was having a really weird issue with pi-hole and the fix I discovered was even more strange, but maybe you can help me figure out why this works this way?

So, my Odroid HC-1, running pi-hole and a Nextcloud stack would always fail to come back properly after a reboot because /etc/tmpfiles.d/pi-hole.conf would somehow not get executed and so there would be no dns and that would screw everything up. Now I experimented with various things and finally found that if I removed all the trailing spaces and '-' in that file, my problems would go away. So I guess I'm posting this both for awareness and because maybe someone could help me figure out why these were problematic?