Your Pi-hole has two-factor authentication enabled. You have to
- enter a valid TOTP
+ enter a valid TOTP
token in addition to your password. You see this message because your
token was incorrect or has already expired.
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.
+ 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.
Make sure you have set up conditional forwarding in this case.
@@ -189,7 +189,7 @@ mg.include('scripts/lua/settings_header.lp','r')
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.
+ here.
@@ -219,7 +219,7 @@ mg.include('scripts/lua/settings_header.lp','r')
whereas an even wider network of 10.0.0.1 - 10.255.255.255 results in 10.0.0.0/8.
Setting up IPv6 ranges is exactly similar to setting up IPv4 here and fully supported.
Feel free to reach out to us on our
- Discourse forum
+ Discourse forum
in case you need any assistance setting up local host name resolution for your particular system.
You can also specify a local domain name (like fritz.box) to ensure queries to
devices ending in your local domain name will not leave your network, however, this is optional.
diff --git a/settings-system.lp b/settings-system.lp
index 1e6eb27f..c1c32ec4 100644
--- a/settings-system.lp
+++ b/settings-system.lp
@@ -191,7 +191,7 @@ mg.include('scripts/lua/settings_header.lp','r')
-->