Package Details: pi-hole-core 6.0.6-1

Git Clone URL: https://aur.archlinux.org/pi-hole-core.git (read-only, click to copy)
Package Base: pi-hole-core
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
Licenses: EUPL-1.2
Conflicts: pi-hole-server, pi-hole-standalone
Provides: pi-hole-server, pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 119
Popularity: 2.56
First Submitted: 2025-02-21 17:31 (UTC)
Last Updated: 2025-03-30 17:07 (UTC)

Pinned Comments

max.bra commented on 2025-02-21 21:44 (UTC)

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.

max.bra commented on 2025-02-21 17:56 (UTC)

to update to pi-hole 6, please use pi-hole-core pi-hole-ftl and pi-hole-web packages.

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 87 Next › Last »

dmellado commented on 2022-03-23 10:38 (UTC) (edited on 2022-03-23 10:39 (UTC) by dmellado)

Hi! I've been checking that using the latest package compiled I'm getting duplicated entries in 01-pihole.conf from the upstream DNS'. Rather than removing them it's just stacking them out in the file.

i.e.

addn-hosts=/etc/pihole/local.list
addn-hosts=/etc/pihole/custom.list
localise-queries
no-resolv
cache-size=10000
log-queries
log-facility=/run/log/pihole/pihole.log
local-ttl=2
log-async
# If a DHCP client claims that its name is "wpad", ignore that.
# This fixes a security hole. see CERT Vulnerability VU#598349
dhcp-name-match=set:wpad-ignore,wpad
dhcp-ignore-names=tag:wpad-ignore
domain-needed
expand-hosts
bogus-priv
local-service
rev-server=192.168.1.0/24,192.168.1.1
server=/lcg.lan/192.168.1.1
server=1.1.1.1
server=1.0.0.1
domain-needed
expand-hosts
bogus-priv
local-service
rev-server=192.168.1.0/24,192.168.1.1
server=/lcg.lan/192.168.1.1
server=127.0.0.1#5335
server=1.0.0.1
domain-needed
expand-hosts
bogus-priv
local-service

max.bra commented on 2022-03-14 09:05 (UTC)

@m_st i don't think so, but anyway try: from the snapshot use dnsmasq.include as your "new default" 01-pihole.conf replacing yours and see what happens.

m_st commented on 2022-03-14 08:59 (UTC)

@max.bra No, I didn't find out. Maybe it was caused by editing the file manually before?

max.bra commented on 2022-03-06 16:57 (UTC)

@m_st mmh, no duplication here... can you find the triggering cause? I mean if is there a setting (e.g. Allow only local requests) which if checked triggers duplication...

m_st commented on 2022-03-06 16:52 (UTC)

@max.bra The new package did write to the config file, while still duplicating the entries in there. But now everything seems to be working and it doesn't use the google DNS anymore. Thanks for your help!

max.bra commented on 2022-03-06 11:39 (UTC)

@jxir no I was not!! Thanks for reporting. I think i've issued a CTRL+D instead of CTRL+S...

jxir commented on 2022-03-06 11:33 (UTC)

Hi @max.bra, I think you didn't mean to remove the depends variable in revision 3 ?

max.bra commented on 2022-03-06 10:42 (UTC)

yes it's a sudoers related permission problem. please try revision 3.

m_st commented on 2022-03-06 10:18 (UTC)

@max.bra That's what I thought aswell, I didn't see this file before and only used the gui. The file looks exactly like that.

I configured it in the web interface and restarted pi-hole, but this didn't change 01-pihole.conf. Also I now got this error: Warning in dnsmasq core: no upstream servers configured

So it seems the web interface does not (or cannot) write anything to this config file. However, the selection of upstream servers in the web interface is still being saved (I guess somewhere in the database?).

Should pi-hole actually write to this config file? Then maybe there is a permission problem?

max.bra commented on 2022-03-06 10:01 (UTC)

01-pihole.conf seems to be a bit messed up. Was it a problem in the copy paste or do I really see a lot of duplicate entries? ... and there is also a google server (8.8.4.4), the one you were probably looking for. Try to delete everything underneath:

# If a DHCP client claims that its name is "wpad", ignore that.
# This fixes a security hole. see CERT Vulnerability VU#598349
dhcp-name-match=set:wpad-ignore,wpad
dhcp-ignore-names=tag:wpad-ignore

and reconfigure DNS via web interface.

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 87 Next › Last »