diff --git a/scripts/pi-hole/js/settings-advanced.js b/scripts/pi-hole/js/settings-advanced.js index 7b8e1db1..5607cb71 100644 --- a/scripts/pi-hole/js/settings-advanced.js +++ b/scripts/pi-hole/js/settings-advanced.js @@ -49,12 +49,9 @@ function generateRow(topic, key, value) { } // else: we have a setting we can display - var row = - '
" +
+ topic.name +
+ ")" +
+ "| + DHCPDISCOVER: + | ++ |
|---|---|
| + DHCPOFFER: + | ++ |
| + DHCPREQUEST: + | ++ |
| + DHCPACK: + | ++ |
| + DHCPNAK: + | ++ |
| + DHCPDECLINE: + | ++ |
| + DHCPINFORM: + | ++ |
| + DHCPRELEASE: + | ++ |
| + DHCPNOANSWER: + | ++ |
| + BOOTP: + | ++ |
| + PXE: + | ++ |
| + Allocated / pruned IPv4 leases: + | +/ + + | +
| + Allocated / pruned IPv6 leases: + | +/ + + | +
| - DHCPDISCOVER: - | -- |
|---|---|
| - DHCPOFFER: - | -- |
| - DHCPREQUEST: - | -- |
| - DHCPACK: - | -- |
| - DHCPNAK: - | -- |
| - DHCPDECLINE: - | -- |
| - DHCPINFORM: - | -- |
| - DHCPRELEASE: - | -- |
| - DHCPNOANSWER: - | -- |
| - BOOTP: - | -- |
| - PXE: - | -- |
| - Allocated / pruned IPv4 leases: - | -/ - - | -
| - Allocated / pruned IPv6 leases: - | -/ - - | -
These options are dangerous on devices - directly connected to the Internet such as cloud instances and are only safe if your - Pi-hole is properly firewalled. In a typical at-home setup where your Pi-hole is - located within your local network (and you have not forwarded port 53 - in your router!) they are safe to use.
-See our documentation for further technical details.
-Tells Pi-hole to never forward A or AAAA queries for plain
- names, without dots or domain parts, to upstream nameservers. If
- the name is not known from /etc/hosts or DHCP then a "not found"
- answer is returned.
- If Conditional Forwarding is enabled, unticking this box may cause a partial
- DNS loop under certain circumstances (e.g. if a client would send TLD DNSSEC queries).
All reverse lookups for private IP ranges (i.e., 192.168.0.x/24, etc.)
- which are not found in /etc/hosts or the DHCP leases are answered
- with "no such domain" rather than being forwarded upstream. The set
- of prefixes affected is the list given in RFC6303.
Important: Enabling these two options may increase your privacy, - but may also prevent you from being able to access - local hostnames if the Pi-hole is not used as DHCP server.
-Validate DNS replies and cache DNSSEC data. When forwarding DNS - queries, Pi-hole requests the DNSSEC records needed to validate - the replies. If a domain fails validation or the upstream does not - support DNSSEC, this setting can cause issues resolving domains. - Use an upstream DNS server which supports DNSSEC when activating DNSSEC. Note that - the size of your log might increase significantly - when enabling DNSSEC. A DNSSEC resolver test can be found - here.
-Block clients making more than queries within - seconds.
-When a client makes too many queries in too short time, it
- gets rate-limited. Rate-limited queries are answered with a
- REFUSED reply and not further processed by FTL
- and prevent Pi-holes getting overwhelmed by rogue clients.
- It is important to note that rate-limiting is happening on a
- per-client basis. Other clients can continue to use FTL while
- rate-limited clients are short-circuited at the same time.
Rate-limiting may be disabled altogether by setting both - values to zero. See - our documentation - for further details.
-These options are dangerous on devices + directly connected to the Internet such as cloud instances and are only safe if your + Pi-hole is properly firewalled. In a typical at-home setup where your Pi-hole is + located within your local network (and you have not forwarded port 53 + in your router!) they are safe to use.
+See our documentation for further technical details.
+Tells Pi-hole to never forward A or AAAA queries for plain
+ names, without dots or domain parts, to upstream nameservers. If
+ the name is not known from /etc/hosts or DHCP then a "not found"
+ answer is returned.
+ If Conditional Forwarding is enabled, unticking this box may cause a partial
+ DNS loop under certain circumstances (e.g. if a client would send TLD DNSSEC queries).
All reverse lookups for private IP ranges (i.e., 192.168.0.x/24, etc.)
+ which are not found in /etc/hosts or the DHCP leases are answered
+ with "no such domain" rather than being forwarded upstream. The set
+ of prefixes affected is the list given in RFC6303.
Important: Enabling these two options may increase your privacy, + but may also prevent you from being able to access + local hostnames if the Pi-hole is not used as DHCP server.
+Validate DNS replies and cache DNSSEC data. When forwarding DNS + queries, Pi-hole requests the DNSSEC records needed to validate + the replies. If a domain fails validation or the upstream does not + support DNSSEC, this setting can cause issues resolving domains. + Use an upstream DNS server which supports DNSSEC when activating DNSSEC. Note that + the size of your log might increase significantly + when enabling DNSSEC. A DNSSEC resolver test can be found + here.
+Block clients making more than queries within + seconds.
+When a client makes too many queries in too short time, it
+ gets rate-limited. Rate-limited queries are answered with a
+ REFUSED reply and not further processed by FTL
+ and prevent Pi-holes getting overwhelmed by rogue clients.
+ It is important to note that rate-limiting is happening on a
+ per-client basis. Other clients can continue to use FTL while
+ rate-limited clients are short-circuited at the same time.
Rate-limiting may be disabled altogether by setting both + values to zero. See + our documentation + for further details.
+Make sure your router's DHCP server is disabled when using the Pi-hole DHCP server!
-Enable this option to enable IPv6 support for the Pi-hole DHCP server. This will allow the Pi-hole to hand out IPv6 addresses to clients and also provide IPv6 router advertisements (RA) to clients. This option is only useful if the Pi-hole is configured with an IPv6 address.
+Make sure your router's DHCP server is disabled when using the Pi-hole DHCP server!
+The DNS domains for the DHCP server. If no domain is specified, then any DHCP hostname with a domain part (i.e., with a period) will be disallowed. If a domain is specified, then hostnames with a domain parts matching the domain here are allowed. In addition, when a suffix is set then hostnames without a domain part have the suffix added as an optional domain part.
-The lease time can be in seconds, minutes (e.g., "45m"), hours (e.g., "1h"), days (like "2d"), or even weeks ("1w"). You may also use "infinite" as string but be aware of the drawbacks: assigned addresses are will only be made available again after the lease time has passed or when leases are manually deleted below.
-The DHCPv4 rapid commit option allows the Pi-hole DHCP server to assign an IP address to a client right away. This can noteably speed up the address assignment process and you will notice, e.g., faster WiFi joins in your network. This option should only be enabled if the Pi-hole DHCP server is the only DHCP server in your network.
+Enable this option to enable IPv6 support for the Pi-hole DHCP server. This will allow the Pi-hole to hand out IPv6 addresses to clients and also provide IPv6 router advertisements (RA) to clients. This option is only useful if the Pi-hole is configured with an IPv6 address.
+The DNS domains for the DHCP server. If no domain is specified, then any DHCP hostname with a domain part (i.e., with a period) will be disallowed. If a domain is specified, then hostnames with a domain parts matching the domain here are allowed. In addition, when a suffix is set then hostnames without a domain part have the suffix added as an optional domain part.
+The lease time can be in seconds, minutes (e.g., "45m"), hours (e.g., "1h"), days (like "2d"), or even weeks ("1w"). You may also use "infinite" as string but be aware of the drawbacks: assigned addresses are will only be made available again after the lease time has passed or when leases are manually deleted below.
+The DHCPv4 rapid commit option allows the Pi-hole DHCP server to assign an IP address to a client right away. This can noteably speed up the address assignment process and you will notice, e.g., faster WiFi joins in your network. This option should only be enabled if the Pi-hole DHCP server is the only DHCP server in your network.
+