Arch Linux User Repository

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.

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

@deemon

Put the domain facebook.com in a file called blocklist (you can add more domains by adding a domain per line)

Then, in a shell script:

#!/usr/bin/env bash

blockDomains=$(<blocklist)

for domain in ${blockDomains[@]}; do
  /usr/local/bin/pihole --wild $domain
done

If you want to remove a domain, just add -d flag to the pihole command:

/usr/local/bin/pihole --wild -d $domain

The entry in the domains list will look like:

(\.|^)facebook\.com$

To deny all domains from a custom Regex:

pihole --regex "[a-z]test.com"

Can someone explain to me, how to add a regex blacklist entry to pihole? Pihole own website is complete mess and at best explains how to make regex patterns ( https://docs.pi-hole.net/regex/ ), but nowhere is written or given any examples, how or where to insert them exactly??

So, can someone please give me a command line example, how to add an regex entry for example for \.googlevideo\.com$ to the regex blacklist? (Preferably so it doesn't get nuked by gravity.db update.)

@max.bra Thank you for the clarification and detailed explanation. I completely understand that the Arch philosophy emphasizes user control over automation, and I appreciate the effort put into aligning the AUR package with those principles.

I also see your point about using a supported distribution or a container for those who need features like auto-generation of configuration files. It’s helpful to know that the package behaves as intended within the context of Arch Linux.

Thanks again for maintaining the AUR package and for restoring the backup mode (which I don’t need, but maybe others do) — it’s much appreciated!

As you can read below, a few months ago in August, someone complained about the handling of 01-pihole.conf in backup mode. Today, someone is complaining about the same file outside of backup mode.

Archlinux is NOT a distribution supported by the pi-hole project. Archlinux requires configuration files to be managed by the user, including pacsave and pacnew. Archlinux (including AUR) is based on the installation of clear and simple packages, with no particular use of automation whatsoever, whose resulting configuration files are always delegated to the end user to manage.

There is nothing wrong with the generation of the 01-pihole.conf file simply because it is not generated as the official installation script does. Just see it in the AUR files.

I will now restore the backup mode as it has always been and call it a day.

If anyone needs debug mode, restore mode and auto-generation of configuration files, I strongly advise them to use a box with a supported distribution and/or use a container.

@trainzkid I’m not the maintainer of this AUR package, but I agree with your observation. It seems that the Arch Linux version of Pi-hole is packaged differently from the official Pi-hole installation (via the basic-install.sh script). The Arch version seems to lack certain automation features, such as the automatic creation or update of /etc/dnsmasq.d/01-pihole.conf based on setupVars.conf.

This might be because Arch Linux software typically follows the KIS philosophy, which gives users more control but also places more responsibility on them.

That said, I could be wrong—perhaps @max.bra can clarify this better.

@krischel (or whomever has the answer)

According to the header in /etc/dnsmasq.d/01-pihole.conf, that config file should be created automatically from /etc/pihole/setupVars.conf. Why is the Arch version not doing this? What is different about the Arch version that it doesn't create this file correctly? What am I missing?

Hi, I have the same problem as @trainzkid, the 01-pihole.conf file was overwritten and with them the upstream dns settings were lost.

@max.bra could you add etc/dnsmasq.q/01-pihole.conf to backup files in the PKGCONFIG?

Thanks.

@trainzkid It is indeed advisable to store custom configurations in a separate file to protect them from being overwritten during updates. In this case, as I mentioned earlier, you can use /etc/dnsmasq.d/99-edns.conf because configuration files in dnsmasq are loaded alphabetically, and files with higher numbers take precedence over others.

@max.bra

Just lost DNS again following an update. Am I expected to have to correct configs after EVERY update (because /etc/dnsmasq.d/01-pihole.conf gets auto rebuilt)?

Concerns the cache limit.

I do this with an own configuration file /etc/dnsmasq.d/99-edns.conf so that the file is not overwritten in the event of an update. It currently looks like this for me:

edns-packet-max=1232
dns-forward-max=300
cache-size=10000