mirror of
https://github.com/pi-hole/docs.git
synced 2024-12-06 19:27:12 +01:00
Update various pihole restartdns references
Signed-off-by: Adam Warner <me@adamwarner.co.uk>
This commit is contained in:
@@ -9,7 +9,7 @@ Pi-hole *FTL*DNS currently supports the following modes for blocking queries:
|
||||
Each mode has their advantages and drawbacks which will be discussed in detail below.
|
||||
|
||||
!!! note
|
||||
In order to configure a blocking mode, you must edit the *FTL*DNS configuration file (`/etc/pihole/pihole-FTL.conf`). Once you've made any changes to the blocking mode, you must restart Pi-hole with `pihole restartdns`.
|
||||
In order to configure a blocking mode, you must edit the *FTL*DNS configuration file (`/etc/pihole/pihole-FTL.conf`). Once you've made any changes to the blocking mode, you must restart Pi-hole FTL (e.g `sudo service pihole-FTL restart` `sudo systemctl restart pihole-FTL`).
|
||||
|
||||
## Pi-hole's unspecified IP or NULL blocking mode
|
||||
|
||||
|
||||
@@ -133,7 +133,7 @@ Warnings commonly seen in `dnsmasq`'s log file (`/var/log/pihole/pihole.log`) an
|
||||
edns-packet-max=1232
|
||||
```
|
||||
|
||||
After running `pihole restartdns` your Pi-hole will not even try larger packet sizes (the default is 4096). Check out our [unbound guide](../guides/dns/unbound.md) for a comment about the particular value of `1232` or reference [this comment](https://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803/31) regarding the various allowed packet sizes for the various upstream DNS servers.
|
||||
After restarting pihole-FTL it will not even try larger packet sizes (the default is 4096). Check out our [unbound guide](../guides/dns/unbound.md) for a comment about the particular value of `1232` or reference [this comment](https://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803/31) regarding the various allowed packet sizes for the various upstream DNS servers.
|
||||
|
||||
!!! warning "Ignoring query from non-local network"
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ In this example, we describe how to set up a blocking rule for three specific cl
|
||||
Don't forget to run
|
||||
|
||||
```bash
|
||||
pihole restartdns reload-lists
|
||||
pihole reloadlists
|
||||
```
|
||||
|
||||
after your database modifications to have FTL flush its internal domain-blocking cache (separate from the DNS cache).
|
||||
|
||||
@@ -28,7 +28,7 @@ If you want a recognizable hostname for the Tor DNS in your Pi-hole GUI statisti
|
||||
Restart Pi-hole DNS Server for the `/etc/hosts` changes to take effect
|
||||
|
||||
```bash
|
||||
sudo pihole restartdns
|
||||
sudo service pihole-FTL restart
|
||||
```
|
||||
|
||||
## Testing your configuration
|
||||
|
||||
+2
-2
@@ -16,9 +16,9 @@ There are two locations where regex filters are important:
|
||||
*FTL*DNS reads in regular expression filters from the two [`regex` database views](../database/domain-database/index.md).
|
||||
To tell *FTL*DNS to reload the list of regex filters, either:
|
||||
|
||||
- Execute `pihole restartdns reload-lists` or
|
||||
- Execute `pihole reloadlists` or
|
||||
- Send `SIGHUP` to `pihole-FTL` (`sudo killall -SIGHUP pihole-FTL`) or
|
||||
- Restart the service (`sudo service pihole-FTL restart`)
|
||||
- Restart the service (`sudo service pihole-FTL restart` or `sudo systemctl restart pihole-FTL`)
|
||||
|
||||
The first command is to be preferred as it ensures that the DNS cache itself remains intact. Hence, it is also the fastest of the available options.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user