Pi-Hole/docs
1
0
Fork 0
mirror of https://github.com/pi-hole/docs.git synced 2025-12-19 18:58:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos in docs

Browse Source 
Signed-off-by: Rob Gill <rrobgill@protonmail.com>
This commit is contained in:
Rob Gill
2025-03-24 14:13:09 +10:00
parent f141fc253e
commit 4a3986fe91
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -42,7 +42,7 @@ Please make sure you fork the repo and change the clone URL in the example below
pip3 install -r requirements.txt
```
- Enter the virtual enviorment (if exited):
- Enter the virtual environment (if exited):
```bash
source .venv/bin/activate

2
docs/abbreviations.md
View File

@@ -3,7 +3,7 @@
*[API]: Application Programming Interface (a set of subroutine definitions, protocols, and tools for building application software)
*[CSRF]: Cross-site request forgery
*[DNS]: Domain Name Service (decentralized naming system for computers, services, or other resources connected to the Internet)
*[DnyDNS]: Dynamic DNS record pointing to a frequently changing IP address
*[DynDNS]: Dynamic DNS record pointing to a frequently changing IP address
*[DHCP]: Dynamic Host Configuration Protocol (network management protocol for configuring Internet Protocol version 4 (IPv4) hosts with IP addresses)
*[DHCPv6]: Dynamic Host Configuration Protocol version 6 (a network protocol for configuring Internet Protocol version 6 (IPv6) hosts with IP addresses)
*[FTL]: Pi-hole's Faster Than Light daemon

2
docs/ftldns/dnsmasq_warn.md
View File

@@ -179,7 +179,7 @@ Warnings commonly seen in `dnsmasq`'s log file (`/var/log/pihole/pihole.log`) an
!!! warning "LOUD WARNING: listening on `ADDRESS` may accept requests via interfaces other than `IFNAME`"
When using `bind-interfaces`, the only access control is the addresses `dnsmasq` is listening on. There's nothing to avoid a query to the address of an internal interface arriving via an external interface where we don't want to accept queries, except that in the usual case the addresses of internal interfaces are RFC1918. When `bind-interfaces` in use, and we listen on an address that looks like it's probably globally routeable, this warning is printed.
When using `bind-interfaces`, the only access control is the addresses `dnsmasq` is listening on. There's nothing to avoid a query to the address of an internal interface arriving via an external interface where we don't want to accept queries, except that in the usual case the addresses of internal interfaces are RFC1918. When `bind-interfaces` in use, and we listen on an address that looks like it's probably globally routable, this warning is printed.
!!! warning "LOUD WARNING: use --bind-dynamic rather than --bind-interfaces to avoid DNS amplification attacks via these interface(s)"

2
docs/guides/vpn/openvpn/dynDNS.md
View File

@@ -69,7 +69,7 @@ daemon_interval="300"
### Example: Strato DynDNS
In the following, we give an example of how to set up `ddclient` using the German Internet hosting provider Strato. First, you need to create a subdomain. Then you need to enable DnyDNS for this domain:
In the following, we give an example of how to set up `ddclient` using the German Internet hosting provider Strato. First, you need to create a subdomain. Then you need to enable DynDNS for this domain:
![](Strato-DynDNS-Domain.png)