But the dashboard seems to register none of the requests- all queries and general activity is uniform, and the 'Total' quary tally does not update either.
See screenshot.
From a client that you believe should be connected to the Pi-Hole for DNS, from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of
My router DNS settings point to my pi-hole IP and to cloudflare. OK thanks- so at least we know I'm somehow misconfigured, and that this isn't just a strange glitch.
Pi-hole should be your only DNS server. Given multiple DNS servers, clients are free to use any of them at any time, and this can result in some DNS traffic bypassing Pi-hole.
What was the exact command you ran?
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
I gave up on setting it up through the router, and after changing the DNS settings locally on the host, some blockings are showing up. It does seem to work then, only not optimally for me (through the router).
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
* Received 288 bytes from eth0:192.168.1.1
Offered IP address: 192.168.1.9
Server IP address: N/A
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.1
lease-time: 3192 ( 53m 12s )
netmask: 255.255.255.0
router: 192.168.1.1
dns-server: 192.168.1.1
domain-name: "HomeGateway"
--- end of options ---
DHCP packets received on interface lo: 0
DHCP packets received on interface wlan0: 0
DHCP packets received on interface eth0: 1
You have the option of using Pi-hole as your DHCP server.