xavye/ascoetpi
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Actualiser pi-hole/Install.md

Browse Source
This commit is contained in:
xavye
2026-01-15 16:46:36 +00:00
parent 6026e2edeb
commit 08915e09c4
1 changed files with 27 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
pi-hole/readme.md → pi-hole/Install.md
View File

@@ -90,3 +90,30 @@ ufw<span class="w"> </span>allow<span class="w"> </span><span class="m">123</spa
<p><abbr title="Internet Protocol version 6 (addresses like 2001:db8::ff00:42:8329)">IPv6</abbr> (include above <abbr title="Internet Protocol version 4 (addresses like 192.168.0.1)">IPv4</abbr> rules):</p>
<div class="highlight"><pre><span></span><code>ufw<span class="w"> </span>allow<span class="w"> </span><span class="m">546</span>:547/udp
</code></pre></div>
<h1>Post-Install</h1>
<h2 id="making-your-network-take-advantage-of-pi-hole">Making your network take advantage of Pi-hole<a class="headerlink" href="#making-your-network-take-advantage-of-pi-hole" title="Permanent link">&para;</a></h2>
<p>Once the installer has been run, you will need to <a href="https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245">configure your router to have <strong><abbr title="Dynamic Host Configuration Protocol (network management protocol for configuring Internet Protocol version 4 (IPv4) hosts with IP addresses)">DHCP</abbr> clients use Pi-hole as their <abbr title="Domain Name Service (decentralized naming system for computers, services, or other resources connected to the Internet)">DNS</abbr> server</strong></a> which ensures all devices connected to your network will have content blocked without any further intervention.</p>
<p>If your router does not support setting the <abbr title="Domain Name Service (decentralized naming system for computers, services, or other resources connected to the Internet)">DNS</abbr> server, you can <a href="https://discourse.pi-hole.net/t/how-do-i-use-pi-holes-built-in-dhcp-server-and-why-would-i-want-to/3026">use Pi-hole's built-in <abbr title="Dynamic Host Configuration Protocol (network management protocol for configuring Internet Protocol version 4 (IPv4) hosts with IP addresses)">DHCP</abbr> server</a>; just be sure to disable <abbr title="Dynamic Host Configuration Protocol (network management protocol for configuring Internet Protocol version 4 (IPv4) hosts with IP addresses)">DHCP</abbr> on your router first (if it has that feature available).</p>
<p>As a last resort, you can manually set each device to use Pi-hole as its <abbr title="Domain Name Service (decentralized naming system for computers, services, or other resources connected to the Internet)">DNS</abbr> server.</p>
<h2 id="making-your-pi-hole-host-use-pi-hole">Making your Pi-hole host use Pi-hole<a class="headerlink" href="#making-your-pi-hole-host-use-pi-hole" title="Permanent link">&para;</a></h2>
<p>Pi-hole will not be used by the host automatically after installation. To have the host resolve through Pi-hole and your configured blocking lists, you can make the host use Pi-hole as upstream <abbr title="Domain Name Service (decentralized naming system for computers, services, or other resources connected to the Internet)">DNS</abbr> server:</p>
<div class="admonition warning">
<p class="admonition-title">Warning</p>
<p>If your Pi-hole host is using Pi-hole as upstream <abbr title="Domain Name Service (decentralized naming system for computers, services, or other resources connected to the Internet)">DNS</abbr> server and Pi-hole fails, your host loses <abbr title="Domain Name Service (decentralized naming system for computers, services, or other resources connected to the Internet)">DNS</abbr> resolution. This can prevent successful repair attempts, e.g. by <code>pihole -r</code> as it needs a working internet connection.</p>
</div>
<p>If your <abbr title="Operating system">OS</abbr> uses <code>dhcpcd</code> for network configuration, you can add to your <code>/etc/dhcpcd.conf</code></p>
<div class="highlight"><pre><span></span><code>static domain_name_servers=127.0.0.1
</code></pre></div>
<h2 id="adding-your-local-user-to-the-pihole-group">Adding your local user to the 'pihole' group<a class="headerlink" href="#adding-your-local-user-to-the-pihole-group" title="Permanent link">&para;</a></h2>
<p>Pi-hole v6 uses a new <abbr title="Application Programming Interface (a set of subroutine definitions, protocols, and tools for building application software)">API</abbr> for authentication. All <abbr title="Command-line Interface">CLI</abbr> commands use this <abbr title="Application Programming Interface (a set of subroutine definitions, protocols, and tools for building application software)">API</abbr> instead of e.g. direct database manipulation. If a password is set for <abbr title="Application Programming Interface (a set of subroutine definitions, protocols, and tools for building application software)">API</abbr> access, the <abbr title="Command-line Interface">CLI</abbr> commands also need to authenticate. To avoid entering the password everytime on <abbr title="Command-line Interface">CLI</abbr>, Pi-hole allows users which are members of the 'pihole' group to authenticate without manually entering the password (this can be disabled by setting <code>webserver.api.cli_pw</code> to <code>false</code>.)
To add your local user to the 'pihole' group use the following command</p>
<p>For Debian/Ubuntu/Raspberry Pi <abbr title="Operating system">OS</abbr>/Armbian/Fedora/CentOS</p>
<div class="highlight"><pre><span></span><code>sudo usermod -aG pihole $USER
</code></pre></div>
<p>For Alpine</p>
<div class="highlight"><pre><span></span><code>sudo addgroup pihole $USER
</code></pre></div>