Network Information

Pi-hole Ethernet Interface: unknown
Pi-hole IPv4 address: unknown
Pi-hole IPv6 address: unknown
Pi-hole hostname: id.andiim3.com

FTL Information

FTL version: v6.5
Process identifier (PID): 2353227
Time FTL started: Fri Apr 3 20:34:41 2026
User / Group: pihole / pihole
Total CPU utilization: 2.2%
Memory utilization: 4.0%
Used memory: 153.05 MB
DNS cache size:  
DNS cache insertions:  
DNS cache evictions:  
See also our DNS cache documentation.

Adlists used to generate Pi-hole's Gravity

Please use the group management pages to edit the adlists used by Pi-hole.

DHCP Settings


From
To
Router

Advanced DHCP settings

Domain
Lease time in hours

Hint: 0 = infinite, 24 = one day, 168 = one week, 744 = one month, 8760 = one year

 
 

DHCP leases

MAC address IP address Hostname

MAC address IP address Hostname

Specifying the MAC address is mandatory and only one entry per MAC address is allowed. If the IP address is omitted and a host name is given, the IP address will still be generated dynamically and the specified host name will be used. If the host name is omitted, only a static lease will be added.

Upstream DNS Servers

IPv4 IPv6 Name
Google (ECS, DNSSEC)
OpenDNS (ECS, DNSSEC)
Level3
Comodo
DNS.WATCH (DNSSEC)
Quad9 (filtered, DNSSEC)
Quad9 (unfiltered, no DNSSEC)
Quad9 (filtered, ECS, DNSSEC)
Cloudflare (DNSSEC)

ECS (Extended Client Subnet) defines a mechanism for recursive resolvers to send partial client IP address information to authoritative DNS name servers. Content Delivery Networks (CDNs) and latency-sensitive services use this to give geo-located responses when responding to name lookups coming through public DNS resolvers. Note that ECS may result in reduced privacy.

Upstream DNS Servers

Custom 1 (IPv4)
Custom 2 (IPv4)
Custom 3 (IPv6)
Custom 4 (IPv6)

Interface listening behavior

Note that the last option should not be used on devices which are directly connected to the Internet. This option is safe if your Pi-hole is located within your local network, i.e. protected behind your router, and you have not forwarded port 53 to this device. In virtually all other cases you have to make sure that your Pi-hole is properly firewalled.

Advanced DNS settings

When there is a Pi-hole domain set and this box is ticked, this asks FTL that this domain is purely local and FTL may answer queries from /etc/hosts or DHCP leases but should never forward queries on that domain to any upstream servers.

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.


Conditional forwarding

If not configured as your DHCP server, Pi-hole typically won't be able to determine the names of devices on your local network. As a result, tables such as Top Clients will only show IP addresses.

One solution for this is to configure Pi-hole to forward these requests to your DHCP server (most likely your router), but only for devices on your home network. To configure this we will need to know the IP address of your DHCP server and which addresses belong to your local network. Exemplary input is given below as placeholder in the text boxes (if empty).

If your local network spans 192.168.0.1 - 192.168.0.255, then you will have to input 192.168.0.0/24. If your local network is 192.168.47.1 - 192.168.47.255, it will be 192.168.47.0/24 and similar. If your network is larger, the CIDR has to be different, for instance a range of 10.8.0.1 - 10.8.255.255 results in 10.8.0.0/16, 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 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. The local domain name must match the domain name specified in your DHCP server for this to work. You can likely find it within the DHCP settings.

Local network in CIDR notation IP address of your DHCP server (router) Local domain name (optional)

API settings

Top Lists

Exclude the following domains from being shown in

Query Log

Web interface settings

Interface appearance

Administrator Email Address

Styling (auto saved, per-browser)

Checkbox and radio buttons

CPU Temperature Unit

Privacy settings

DNS resolver privacy level

Specify if DNS queries should be anonymized, available options are:

Gives maximum amount of statistics

This disables the Top Domains and Top Ads tables on the dashboard

This disables all tables on the dashboard

No history is saved at all to the database, and nothing is shown in the query log. Also, there are no top item lists.

The privacy level may be increased at any time without having to restart the DNS resolver. However, note that the DNS resolver needs to be restarted when lowering the privacy level. This restarting is automatically done when saving.

Backup

Backup your Pi-hole configuration (settings & lists) as a downloadable archive

Restore

Upload only Pi-hole backup files.