Skip to content

Commit b9a2fe1

Browse files
yubiuseryubiuser
authored
Merge pull request #1027 from pi-hole/dependabot/pip/master/pip-dependencies-641c6ff211
Bump the pip-dependencies group across 1 directory with 2 updates
2 parents 9f2fe73 + 160567c commit b9a2fe1

File tree

12 files changed

+20
-17
lines changed

12 files changed

+20
-17
lines changed

‎.github/workflows/ci.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ jobs:
4141
run: npm ci
4242

4343
- name: Build docs
44-
run: mkdocs build
44+
run: mkdocs build --strict
4545

4646
- name: Test
4747
run: npm test

‎docs/core/pihole-command.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Pi-hole makes use of many commands, and here we will break down those required t
2929
| [Version](#version) | `pihole version` |
3030
| [Uninstall](#uninstall) | `pihole uninstall` |
3131
| [Status](#status) | `pihole status` |
32-
| [Enable & Disable](#enable-&-disable) | `pihole enable` <!-- markdownlint-disable-line MD051 --> |
32+
| [Enable & Disable](#enable-disable) | `pihole enable` <!-- markdownlint-disable-line MD051 --> |
3333
| [Restart DNS](#restart-dns) | `pihole restartdns` |
3434
| [Checkout](#checkout) | `pihole checkout` |
3535

‎docs/database/ftl.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ ID | Resource Record (a.k.a. query type)
107107
15 | `SVCB`
108108
16 | `HTTPS`
109109

110-
Any other query type will be stored with an offset of 100, i.e., `TYPE66` will be stored as `166` in the database (see [pi-hole/FTL #1013](https://github.com/pi-hole/FTL/pull/1013)). This is done to allow for future extensions of the query type list without having to change the database schema. The `OTHER` query type is deprecated since Pi-hole FTL v5.4 (released Jan 2021) and not used anymore. It is kept for backwards compatibility. Note that `OTHER` is still used for the [regex extension `querytype=`](../regex/pi-hole.md#querytype) filter and used for all queries not covered by the above list.
110+
Any other query type will be stored with an offset of 100, i.e., `TYPE66` will be stored as `166` in the database (see [pi-hole/FTL #1013](https://github.com/pi-hole/FTL/pull/1013)). This is done to allow for future extensions of the query type list without having to change the database schema. The `OTHER` query type is deprecated since Pi-hole FTL v5.4 (released Jan 2021) and not used anymore. It is kept for backwards compatibility. Note that `OTHER` is still used for the [regex extension `querytype=`](../regex/pi-hole.md#only-match-specific-query-types) filter and used for all queries not covered by the above list.
111111

112112
### Supported status types
113113

@@ -117,14 +117,14 @@ ID | Status | | Details
117117
1 | Blocked | ❌ | Domain contained in [gravity database](gravity/index.md#gravity-table-gravity)
118118
2 | Allowed | ✅ | Forwarded
119119
3 | Allowed | ✅ | Replied from cache
120-
4 | Blocked | ❌ | Domain matched by a [regex blacklist](gravity/index.md#regex-table-regex) filter
121-
5 | Blocked | ❌ | Domain contained in [exact blacklist](gravity/index.md#blacklist-table-blacklist)
120+
4 | Blocked | ❌ | Domain matched by a [regex blacklist](gravity/index.md#domain-tables-domainlist) filter
121+
5 | Blocked | ❌ | Domain contained in [exact blacklist](gravity/index.md#domain-tables-domainlist)
122122
6 | Blocked | ❌ | By upstream server (known blocking page IP address)
123123
7 | Blocked | ❌ | By upstream server (`0.0.0.0` or `::`)
124124
8 | Blocked | ❌ | By upstream server (`NXDOMAIN` with `RA` bit unset)
125125
9 | Blocked | ❌ | Domain contained in [gravity database](gravity/index.md#gravity-table-gravity)<br>*Blocked during deep CNAME inspection*
126-
10 | Blocked | ❌ | Domain matched by a [regex blacklist](gravity/index.md#regex-table-regex) filter<br>*Blocked during deep CNAME inspection*
127-
11 | Blocked | ❌ | Domain contained in [exact blacklist](gravity/index.md#blacklist-table-blacklist)<br>*Blocked during deep CNAME inspection*
126+
10 | Blocked | ❌ | Domain matched by a [regex blacklist](gravity/index.md#domain-tables-domainlist) filter<br>*Blocked during deep CNAME inspection*
127+
11 | Blocked | ❌ | Domain contained in [exact blacklist](gravity/index.md#domain-tables-domainlist)<br>*Blocked during deep CNAME inspection*
128128
12 | Allowed | ✅ | Retried query
129129
13 | Allowed | ✅ | Retried but ignored query (this may happen during ongoing DNSSEC validation)
130130
14 | Allowed | ✅ | Already forwarded, not forwarding again

‎docs/ftldns/interfaces.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
Pi-hole offers three choices for interface on its dashboard:
44

5-
![Available interface settings](/images/interface-settings.png)
5+
![Available interface settings](../images/interface-settings.png)
66

77
By default, FTL binds the wildcard address. It does this for all options except *Bind only on interface `enp2s0`*. Your Pi-hole then discards requests that it shouldn't reply to. This has the big advantage of working even when interfaces come and go and change address (this happens way more often than one would think).
88

‎docs/guides/dns/cloudflared.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ google.com. 191 IN A 172.217.22.14
154154

155155
Finally, configure Pi-hole to use the local `cloudflared` service as the upstream DNS server by specifying `127.0.0.1#5053` as the Custom DNS (IPv4):
156156

157-
![Screenshot of Pi-hole configuration](/images/DoHConfig.png)
157+
![Screenshot of Pi-hole configuration](../../images/DoHConfig.png)
158158

159159
(don't forget to hit Return or click on `Save`)
160160

‎docs/guides/dns/unbound.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ The first command should give a status report of `SERVFAIL` and no IP address. T
179179

180180
Finally, configure Pi-hole to use your recursive DNS server by specifying `127.0.0.1#5335` as the Custom DNS (IPv4):
181181

182-
![Upstream DNS Servers Configuration](/images/RecursiveResolver.png)
182+
![Upstream DNS Servers Configuration](../../images/RecursiveResolver.png)
183183

184184
(don't forget to hit Return or click on `Save`)
185185

‎docs/guides/misc/benchmark.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The long-term database can be disabled by setting
2929
DBFILE=
3030
```
3131

32-
in `/etc/pihole/pihole-FTL.conf` and running `sudo pihole restartdns` (see also [here](/ftldns/configfile/#dbfile)).
32+
in `/etc/pihole/pihole-FTL.conf` and running `sudo pihole restartdns` (see also [here](../../ftldns/configfile.md/#dbfile)).
3333

3434
### 2.2 Increase DNS cache size
3535

‎docs/guides/vpn/wireguard/client.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -235,6 +235,6 @@ peer: F+80gbmHVlOrU+es13S18oMEX2g= ⬅ Your peer's public key will be differen
235235

236236
## Test for DNS leaks
237237

238-
You should run a DNS leak test on [www.dnsleaktest.com](https://www.dnsleaktest.com) to ensure your WireGuard tunnel does not leak DNS requests (so all are processed by your Pi-hole). The expected outcome is that you should only see DNS servers belonging to the upstream DNS destination you selected in Pi-hole. If you configured [Pi-hole as All-Around DNS Solution](/guides/dns/unbound/), you should only see the public IP address of your WireGuard server and no other DNS server.
238+
You should run a DNS leak test on [www.dnsleaktest.com](https://www.dnsleaktest.com) to ensure your WireGuard tunnel does not leak DNS requests (so all are processed by your Pi-hole). The expected outcome is that you should only see DNS servers belonging to the upstream DNS destination you selected in Pi-hole. If you configured [Pi-hole as All-Around DNS Solution](../../dns/unbound.md), you should only see the public IP address of your WireGuard server and no other DNS server.
239239

240240
See also [What is a DNS leak and why should I care?](https://www.dnsleaktest.com/what-is-a-dns-leak.html) (external link).

‎docs/routers/fritzbox-de.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ eingetragen werden.
134134

135135
![Screenshot der Fritz!Box IPv6 Adressen Einstellungen](../images/routers/fritzbox-ipv6-2-de.png)
136136

137-
## Optional: Erhöhung der Priorität von DNS Anfragen
137+
## Optional: Erhöhung der Priorität von DNS Anfragen {#optional-erhohung-der-prioritat-von-dns-anfragen}
138138

139139
Bei ausgelasteter Internetverbindung werden DNS-Anfragen u.U. stark verzögert bearbeitet. Dies kann in der Fritz!Box durch Hinterlegen von DNS als priorisierter Echtzeitanwendung vermieden werden. Falls nicht bereits geschehen, fügen Sie hierfür zunächst "`DNS`" als neuen Answendungstyp unter
140140

@@ -188,7 +188,7 @@ zwei Zugangsprofile an (z.B. "`Standard`" und "`Unbeschränkt`"). Im Profil "`St
188188
Erweiterte Einstellungen -> Gesperrte Netzwerkanwendungen
189189
```
190190

191-
die [angelegte Netzwerkanwendung "`DNS`"](/routers/fritzbox-de/#optional-erhohung-der-prioritat-von-dns-anfragen) hinzu.
191+
die [angelegte Netzwerkanwendung "`DNS`"](#optional-erhohung-der-prioritat-von-dns-anfragen) hinzu.
192192
Im Profil "`Unbeschränkt`" darf "`DNS`" *nicht* als gesperrt hinterlegt werden.
193193

194194
Nun werden die Zugangsprofile unter

‎docs/routers/fritzbox.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ If not already present, create two access profiles (e.g. "`Standard`" and "`Unre
175175
Internet/Filters/Access Profiles -> Manage and Optimize Access Profiles
176176
```
177177

178-
In the profile "`Standard`" add the network application "`DNS`" ([created above](/routers/fritzbox/#optional-increasing-the-priority-of-dns-requests)) under:
178+
In the profile "`Standard`" add the network application "`DNS`" ([created above](#optional-increasing-the-priority-of-dns-requests)) under:
179179

180180
``` plain
181181
Advanced settings -> Locked network applications

0 commit comments

Comments
 (0)