DHCP Issues: devices using pihole, but no blocking

Help
1

Expected Behaviour:

Blocking on local devices, with pi-hole acting as DHCP server on local network. Ability to access admin interface at http://pi.hole/admin

Actual Behaviour:

No blocking evident, but devices apparently connected sufficiently.
DHCP disabled on primary router (router does not provide functionality to set DNS), DHCP enabled on pi-hole, which has a fixed ip address.
Most local devices indicated as connected to pi-hole, have internet access, but 'Last query' is not correct and log files seem empty (Tail pihole.log).
Unable to access admin interface via http://pi.hole/admin, only via local ip.

Debug Token:

https://tricorder.pi-hole.net/klv36vyf8q

Complete newbie here, attempting my first install tonight. I've searched for hours with no success. Apologies for anything stupid here, but I've searched and searched with no success found in what I've read so far.

2

are you sure the client devices are using pi hole as the only dns
if your on Windows please post the output of ipconfig /all

3

Your debug log shows no DNS traffic coming to Pi-Hole from your network. After you made the DHCP change, did you reboot the router and renew the DHCP lease on all clients?

   [2020-02-06 23:41:20.229 3416] Imported 0 queries from the long-term database
   [2020-02-06 23:41:20.229 3416]  -> Total DNS queries: 0
   [2020-02-06 23:41:20.229 3416]  -> Cached DNS queries: 0
   [2020-02-06 23:41:20.229 3416]  -> Forwarded DNS queries: 0
   [2020-02-06 23:41:20.229 3416]  -> Exactly blocked DNS queries: 0
   [2020-02-06 23:41:20.229 3416]  -> Unknown DNS queries: 0
   [2020-02-06 23:41:20.229 3416]  -> Unique domains: 0
   [2020-02-06 23:41:20.229 3416]  -> Unique clients: 0
   [2020-02-06 23:41:20.229 3416]  -> Known forward destinations: 0
4

are you sure the client devices are using pi hole as the only dns
if your on Windows please post the output of ipconfig /all

On a Mac, here's my ifconfig output:
(For reference, Pi-Hole is on 192.168.178.25 and router on 178.1

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
XHC20: flags=0<> mtu 0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 60:f8:1d:b2:5f:0a 
	inet6 fe80::18e0:d729:c45f:c861%en0 prefixlen 64 secured scopeid 0x5 
	inet6 2001:1c02:2b0b:4800:1cfe:b3e0:7ebe:110 prefixlen 64 autoconf secured 
	inet6 2001:1c02:2b0b:4800:d9d8:be20:d75:15e prefixlen 64 autoconf temporary 
	inet 192.168.178.206 netmask 0xffffff00 broadcast 192.168.178.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
	ether 02:f8:1d:b2:5f:0a 
	media: autoselect
	status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
	ether 7a:3b:da:3e:84:41 
	inet6 fe80::783b:daff:fe3e:8441%awdl0 prefixlen 64 scopeid 0x7 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether 72:00:07:66:9b:40 
	media: autoselect <full-duplex>
	status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=60<TSO4,TSO6>
	ether 72:00:07:66:9b:41 
	media: autoselect <full-duplex>
	status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether 72:00:07:66:9b:40 
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x2
	member: en1 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 8 priority 0 path cost 0
	member: en2 flags=3<LEARNING,DISCOVER>
	        ifmaxaddr 0 port 9 priority 0 path cost 0
	nd6 options=201<PERFORMNUD,DAD>
	media: <unknown type>
	status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 fe80::8728:658b:5c16:cb03%utun0 prefixlen 64 scopeid 0xb 
	nd6 options=201<PERFORMNUD,DAD>

Your debug log shows no DNS traffic coming to Pi-Hole from your network. After you made the DHCP change, did you reboot the router and renew the DHCP lease on all clients?

I believe I did before, but to make sure I've just rebooted the router and have renewed DHCP leases on the devices that I'm able to. Still no luck (although looking at the logs, it looks like there may be some DNS activity).

> 
>    [2020-02-07 08:16:15.019 1443] Imported 10 queries from the long-term database
>    [2020-02-07 08:16:15.019 1443]  -> Total DNS queries: 10
>    [2020-02-07 08:16:15.019 1443]  -> Cached DNS queries: 2
>    [2020-02-07 08:16:15.019 1443]  -> Forwarded DNS queries: 8
>    [2020-02-07 08:16:15.019 1443]  -> Exactly blocked DNS queries: 0
>    [2020-02-07 08:16:15.019 1443]  -> Unknown DNS queries: 0
>    [2020-02-07 08:16:15.019 1443]  -> Unique domains: 4
>    [2020-02-07 08:16:15.019 1443]  -> Unique clients: 1
>    [2020-02-07 08:16:15.019 1443]  -> Known forward destinations: 1

New debug token is: https://tricorder.pi-hole.net/hva46a3zrv

5

This command run on the Mac terminal will show you the true order of name servers in use on your Mac:

scutil --dns

1 Like
6

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.