Devices do not use Pi-hole

Expected Behaviour:

Using pihole in a LXC container in Proxmox. Web GUI comes up normally, pihole is connected to the internet. Have an AT&T router so I wanted to use pihole on device-by-device basis, since turning off DHCP server on router and enabling it in pihole did not work.

Actual Behaviour:

My OnePlus phone connects to Wi-Fi and internet with static IP settings, gateway being the router and DNS the IP address of the pihole. MacBook with the same settings connects to Wi-Fi but not internet. No devices show up as clients in pihole and there is a cross in the clients table in the "Uses Pi-hole" field.

Debug Token:

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

Your debug log shows that Pi-hole is working normally, but has not received any queries from your network.

   [2021-02-01 12:02:03.960 3622M] Imported 1 queries from the long-term database
   [2021-02-01 12:02:03.960 3622M]  -> Total DNS queries: 1
   [2021-02-01 12:02:03.960 3622M]  -> Cached DNS queries: 1
   [2021-02-01 12:02:03.960 3622M]  -> Forwarded DNS queries: 0
   [2021-02-01 12:02:03.960 3622M]  -> Blocked DNS queries: 0
   [2021-02-01 12:02:03.960 3622M]  -> Unknown DNS queries: 0
   [2021-02-01 12:02:03.960 3622M]  -> Unique domains: 1
   [2021-02-01 12:02:03.960 3622M]  -> Unique clients: 1

After you made that change, did you restart the router and renew DHCP leases on all clients? You have a configuration problem in the router settings most likely, and none of the DNS traffic is going to Pi-hole.

From the Macbook terminal (and not via ssh to Pi-hole), what is the output of the following:

scutil --dns

nslookup pi.hole

Thanks for your help, this is what I got from scutil --dns

DNS configuration

resolver #1
  nameserver[0] : 192.168.1.68
  nameserver[1] : 8.8.8.8
  nameserver[2] : 8.8.4.4
  flags    : Request A records
  reach    : 0x00020002 (Reachable,Directly Reachable Address)

>resolver #2
  domain   : local
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300000

>resolver #3
  domain   : 254.169.in-addr.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300200

>resolver #4
  domain   : 8.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300400

>resolver #5
  domain   : 9.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300600

>resolver #6
  domain   : a.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300800

>resolver #7
  domain   : b.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 301000

>DNS configuration (for scoped queries)

>resolver #1
  nameserver[0] : 192.168.1.68
  nameserver[1] : 8.8.8.8
  nameserver[2] : 8.8.4.4
  if_index : 4 (en0)
  flags    : Scoped, Request A records
  reach    : 0x00020002 (Reachable,Directly Reachable Address)

and for nslookup pi.hole I got
>;; connection timed out; no servers could be reached

I restarted the router after enabling the DHCP server on the pihole but it has not done anything.

This is a potential problem. Given multiple DNS servers, clients are free to use any of them.

Do you have either of the Google DNS servers specified on your router (in DNS positions 2 and 3)? If so, remove them.

Yeah, I set these on my macbook so I could access internet, I have tried the same without these DNS server and I can't connect then. Because my router is BGW210 from AT&T, it does not allow changing the DNS, which I assumed would be the issue for pihole not working.

If you can disable the DHCP server on that router, you can use Pi-hole as the system DHCP server. Even if you cannot, you can restrict the DHCP on the router to a single IP (the IP of Pi-hole) and then setup Pi-hole DHCP on a non-overlapping IP range.

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