Package Details: pi-hole-server 4.2.1-3

Git Clone URL: https://aur.archlinux.org/pi-hole-server.git (read-only)
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.1
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 50
Popularity: 2.936943
First Submitted: 2016-01-13 12:50
Last Updated: 2019-02-11 11:54

Pinned Comments

max.bra commented on 2018-02-09 16:45

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 ... Next › Last »

max.bra commented on 2019-02-12 16:08

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

@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

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

Sure thing. Will check!

max.bra commented on 2019-02-12 08:44

@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

@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

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

@Taijian yes, it was a forgetfulness!! thanks for reporting.

Taijian commented on 2019-02-11 11:26

Looking at this package again and checking against the 'official' changelog for 4.2, I noticed that the fix for the wpad vulnerability included in v4.2+ is not included in this package because you opted to not ship the 01-pihole.conf file included with the upstream package but instead replace it with your homebrew version 'dnsmasq.include', which hasn't been updated with this fix. Is there a reason for this that I'm just not seeing, or is this an oversight?

jonandermb commented on 2019-02-08 19:05

Crashing for me here: The -2 patch seemed to mitigate the symptoms a bit, but I get pihole rebooted every 5 minutes or so :(