I was just wondering if the problem was only on ftl... :-D
Search Criteria
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-ghAUR)
- bind-tools (bind-developmentAUR, bind-gitAUR, bind)
- inetutils (inetutils-gitAUR, busybox-coreutilsAUR)
- iproute2 (iproute2-gitAUR, busybox-coreutilsAUR, iproute2-selinuxAUR)
- jq (jq-gitAUR)
- logrotate (logrotate-gitAUR, logrotate-selinuxAUR)
- lsof (lsof-gitAUR)
- netcat (nmap-netcatAUR, openbsd-netcat-gitAUR, gnu-netcat-svnAUR, gnu-netcat, openbsd-netcat)
- perl (perl-gitAUR)
- pi-hole-ftlAUR
- procps-ng (procps-ng-gitAUR, busybox-coreutilsAUR)
- sudo (fake-sudoAUR, polkit-fakesudoAUR, sudo-gitAUR, doas-sudo-shimAUR, doas-sudo-shim-minimalAUR, sudo-hgAUR, sudo-selinuxAUR, fudo-gitAUR)
- git (git-gitAUR, git-glAUR) (make)
- lighttpd (optional) – a secure, fast, compliant and very flexible web-server
- nginx-mainline (nginx-quic-openssl-hgAUR, nginx-quic-libresslAUR) (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)
- 01-pihole.conf
- https://raw.githubusercontent.com/max72bra/pi-hole-server-archlinux-customization/master/arch-server-admin-5.21-4.patch
- https://raw.githubusercontent.com/max72bra/pi-hole-server-archlinux-customization/master/arch-server-core-5.18.3-4.patch
- lighttpd.pi-hole.conf
- mimic_basic-install.sh
- mimic_setupVars.conf.sh
- nginx.pi-hole.conf
- pi-hole-gravity.service
- pi-hole-gravity.timer
- pi-hole-logtruncate.service
- pi-hole-logtruncate.timer
- pi-hole-server-admin-5.21.tar.gz
- pi-hole-server-core-5.18.3.tar.gz
- pi-hole.tmpfile
- piholeDebug.sh
Latest Comments
« First ‹ Previous 1 .. 38 39 40 41 42 43 44 45 46 47 48 .. 82 Next › Last »
max.bra commented on 2019-02-19 20:33 (UTC)
jshap commented on 2019-02-19 20:27 (UTC) (edited on 2019-02-19 20:27 (UTC) by jshap)
same issues as in pi-hole-ftl
, the raw.github.com/max72bra/... links in the PKGBUILD need instead to be raw.githubusercontent.com/max72bra/...
max.bra commented on 2019-02-12 16:08 (UTC)
yes it is! "our" 01-pihole.conf is without dns server and populated during first install. upstream do the same with their install script.
i never replace conf files with .pacnew ones without a check. it's better to "human" merge them with diff like applications.
glad you solved and thanks for reporting.
mystique commented on 2019-02-12 16:06 (UTC)
@erkexzcx
dnsmasq doesn't do encrypted dns (of any type) only straight udp/tcp port 53.
You would need to use something else (dnscrypt-proxy) for the service of encrypted dns.
I would also recommend quad9 vs cloudflare, but you should do you own homework for your own reasons..
And this would be a forum thing (imho) rather than a package discussion..
My 0.02
erkexzcx commented on 2019-02-12 16:00 (UTC)
So basically what I've done was "mv /etc/dnsmasq.d/01-pihole.conf.pacnew /etc/dnsmasq.d/01-pihole.conf" and rebooted (I think). It stopped working.
Now I just executed "pihole -a setdns 8.8.8.8" and settings were overridden in pi-hole. Everything started to work fine.
But because I was using cloudflared DOH DNS service on my computer - I might guess it is the root cause, but it is not - I went to pi-hole settings and put cloudflared settings (they are "127.0.0.1#5053") and once again everything works.
So probably the root cause was messing with "/etc/dnsmasq.d/01-pihole.conf.pacnew"... :)
erkexzcx commented on 2019-02-12 11:55 (UTC)
Sure thing. Will check!
max.bra commented on 2019-02-12 08:44 (UTC) (edited on 2019-02-12 08:44 (UTC) by max.bra)
@erkexzcx oh, about wiki changes: as stated above the server package is not officially upstream supported as the standalone version is.
max.bra commented on 2019-02-12 08:42 (UTC)
@erkexzcx rev. 3 changes cannot lead to DNS resolution loss. i recommend you to check your .pacnew files and this (https://wiki.archlinux.org/index.php/Pi-hole#/etc/hosts)
erkexzcx commented on 2019-02-12 07:17 (UTC)
Looks like pi-hole-server 4.2.1-3 no longer works as DNS server. pi-hole-server 4.2.1-2 worked fine. Now my DNS queries are not being resolved by Pi-Hole.
max.bra commented on 2019-02-11 11:55 (UTC)
@Taijian yes, it was a forgetfulness!! thanks for reporting.
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.