DNS not reachable from LAN, recent Queries showing only container name as Domain

rleidl · November 14, 2018, 5:47pm

Expected Behaviour:
Pihole Container would be reachable from local network and the Webinterface "Recent Queries" shows all Domains that are queried and wether the domain was Blocked or Forwarded. I would think that I can then block (or whitelist) domains wich are not blocked by the lists.

Actual Behaviour:
Pihole not reachable, no access to local network from pihole container. The Webinterface is only showing entries like this:

|2018-11-14 18:29:27|A|pihole-pihole1|localhost|OK (cached)|IP (0.1ms)| Blacklist|
|2018-11-14 18:29:27|AAAA|pihole-pihole1|localhost|OK (cached)|NODATA (0.1ms)| Blacklist|

Debug Token:
1kukywxblx

Pihole in Docker Container on Synology DSM.

Thanks for any help.

R.

jfb · November 14, 2018, 5:56pm

Your Pi-Hole does not appear to be getting any requests from clients other than the Pi-Hole host. From your debug log:

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.
[✗] No IPv6 address(es) found on the eth0 interface.

[i] Default IPv4 gateway: 192.168.2.1
   * Pinging 192.168.2.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

IPV4_ADDRESS=192.168.2.212

What IP address do you have the router/clients using for DNS?

From a client, what is the output of host pi.hole

Can you ping the IP address of the Pi-Hole and receive replies?

ping -c5 192.168.2.212

rleidl · November 14, 2018, 6:19pm

HI, thanks for the quick reply. Here my answers:

DNS/DHCP Config: My clients have the Router 192.168.2.1 as the standard gateway and DNS respectively. Th DHCP server on the router gives itself as gateway and DNS to the Clients. The WAN Port on the router uses 192.168.2.212 (the pihole on my Synology) as DNS.

Output of host pi.hole:
Host pi.hole not found: 3(NXDOMAIN)

Output of ping 192.168.2.212

ping -c5 192.168.2.212
PING 192.168.2.212 (192.168.2.212): 56 data bytes
64 bytes from 192.168.2.212: icmp_seq=0 ttl=64 time=0.289 ms
64 bytes from 192.168.2.212: icmp_seq=1 ttl=64 time=0.399 ms

Thanks

Rainer

rleidl · November 14, 2018, 6:21pm

In front of the formetioned router there is another router (fritzbox) providing the WAN Interface. This is for telephony purposes. The fritzbox uses the providers' DNS Servers. But I think those don't come into play.

jfb · November 14, 2018, 6:23pm

Run this command from the Pi-Hole host terminal and post the last 50 or so lines of the output:

cat /var/log/pihole.log

jfb · November 14, 2018, 6:41pm

The next step I would try is to put a client DNS directly (manually) on the Pi-Hole IP address (bypassing any DNS assignment by the router). If the client connects to Pi-Hole DNS, then the router is causing the problem.

rleidl · November 14, 2018, 6:44pm

Nov 14 19:09:16 dnsmasq[974]: 421 127.0.0.1/35392 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:09:46 dnsmasq[974]: 422 127.0.0.1/46032 query[A] pi.hole from 127.0.0.1
Nov 14 19:09:46 dnsmasq[974]: 422 127.0.0.1/46032 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:10:16 dnsmasq[974]: 423 127.0.0.1/54555 query[A] pi.hole from 127.0.0.1
Nov 14 19:10:16 dnsmasq[974]: 423 127.0.0.1/54555 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:10:46 dnsmasq[974]: 424 127.0.0.1/38392 query[A] pi.hole from 127.0.0.1
Nov 14 19:10:46 dnsmasq[974]: 424 127.0.0.1/38392 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:11:16 dnsmasq[974]: 425 127.0.0.1/46718 query[A] pi.hole from 127.0.0.1
Nov 14 19:11:16 dnsmasq[974]: 425 127.0.0.1/46718 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:11:46 dnsmasq[974]: 426 127.0.0.1/59739 query[A] pi.hole from 127.0.0.1
Nov 14 19:11:46 dnsmasq[974]: 426 127.0.0.1/59739 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:12:16 dnsmasq[974]: 427 127.0.0.1/38806 query[A] pi.hole from 127.0.0.1
Nov 14 19:12:16 dnsmasq[974]: 427 127.0.0.1/38806 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:12:46 dnsmasq[974]: 428 127.0.0.1/43304 query[A] pi.hole from 127.0.0.1
Nov 14 19:12:46 dnsmasq[974]: 428 127.0.0.1/43304 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:13:16 dnsmasq[974]: 429 127.0.0.1/34685 query[A] pi.hole from 127.0.0.1
Nov 14 19:13:16 dnsmasq[974]: 429 127.0.0.1/34685 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:13:46 dnsmasq[974]: 430 127.0.0.1/45280 query[A] pi.hole from 127.0.0.1
Nov 14 19:13:46 dnsmasq[974]: 430 127.0.0.1/45280 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:14:16 dnsmasq[974]: 431 127.0.0.1/59545 query[A] pi.hole from 127.0.0.1
Nov 14 19:14:16 dnsmasq[974]: 431 127.0.0.1/59545 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:14:47 dnsmasq[974]: 432 127.0.0.1/60955 query[A] pi.hole from 127.0.0.1
Nov 14 19:14:47 dnsmasq[974]: 432 127.0.0.1/60955 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:15:17 dnsmasq[974]: 433 127.0.0.1/33037 query[A] pi.hole from 127.0.0.1
Nov 14 19:15:17 dnsmasq[974]: 433 127.0.0.1/33037 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:15:47 dnsmasq[974]: 434 127.0.0.1/35831 query[A] pi.hole from 127.0.0.1
Nov 14 19:15:47 dnsmasq[974]: 434 127.0.0.1/35831 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:16:17 dnsmasq[974]: 435 127.0.0.1/51352 query[A] pi.hole from 127.0.0.1
Nov 14 19:16:17 dnsmasq[974]: 435 127.0.0.1/51352 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:16:47 dnsmasq[974]: 436 127.0.0.1/58604 query[A] pi.hole from 127.0.0.1
Nov 14 19:16:47 dnsmasq[974]: 436 127.0.0.1/58604 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:17:17 dnsmaNov 14 19:20:47 dnsmasq[974]: 444 127.0.0.1/60083 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:21:17 dnsmasq[974]: 445 127.0.0.1/57532 query[A] pi.hole from 127.0.0.1
Nov 14 19:21:17 dnsmasq[974]: 445 127.0.0.1/57532 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:21:47 dnsmasq[974]: 446 127.0.0.1/44733 query[A] pi.hole from 127.0.0.1
Nov 14 19:21:47 dnsmasq[974]: 446 127.0.0.1/44733 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:22:17 dnsmasq[974]: 447 127.0.0.1/40177 query[A] pi.hole from 127.0.0.1
Nov 14 19:22:17 dnsmasq[974]: 447 127.0.0.1/40177 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:22:47 dnsmasq[974]: 448 127.0.0.1/57593 query[A] pi.hole from 127.0.0.1
Nov 14 19:22:47 dnsmasq[974]: 448 127.0.0.1/57593 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:23:17 dnsmasq[974]: 449 127.0.0.1/52770 query[A] pi.hole from 127.0.0.1
Nov 14 19:23:17 dnsmasq[974]: 449 127.0.0.1/52770 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:23:47 dnsmasq[974]: 450 127.0.0.1/59525 query[A] pi.hole from 127.0.0.1
Nov 14 19:23:47 dnsmasq[974]: 450 127.0.0.1/59525 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:24:17 dnsmasq[974]: 451 127.0.0.1/58758 query[A] pi.hole from 127.0.0.1
Nov 14 19:24:17 dnsmasq[974]: 451 127.0.0.1/58758 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:24:47 dnsmasq[974]: 452 127.0.0.1/37004 query[A] pi.hole from 127.0.0.1
Nov 14 19:24:47 dnsmasq[974]: 452 127.0.0.1/37004 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:25:18 dnsmasq[974]: 453 127.0.0.1/59932 query[A] pi.hole from 127.0.0.1
Nov 14 19:25:18 dnsmasq[974]: 453 127.0.0.1/59932 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:25:48 dnsmasq[974]: 454 127.0.0.1/53340 query[A] pi.hole from 127.0.0.1
Nov 14 19:25:48 dnsmasq[974]: 454 127.0.0.1/53340 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:26:18 dnsmasq[974]: 455 127.0.0.1/50544 query[A] pi.hole from 127.0.0.1
Nov 14 19:26:18 dnsmasq[974]: 455 127.0.0.1/50544 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:26:48 dnsmasq[974]: 456 127.0.0.1/47616 query[A] pi.hole from 127.0.0.1
Nov 14 19:26:48 dnsmasq[974]: 456 127.0.0.1/47616 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:27:18 dnsmasq[974]: 457 127.0.0.1/60039 query[A] pi.hole from 127.0.0.1
Nov 14 19:27:18 dnsmasq[974]: 457 127.0.0.1/60039 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:27:48 dnsmasq[974]: 458 127.0.0.1/44442 query[A] pi.hole from 127.0.0.1
Nov 14 19:27:48 dnsmasq[974]: 458 127.0.0.1/44442 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:28:18 dnsmasq[974]: 459 127.0.0.1/43905 query[A] pi.hole from 127.0.0.1
Nov 14 19:28:18 dnsmasq[974]: 459 127.0.0.1/43905 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:28:48 dnsmasq[974]: 460 127.0.0.1/56158 query[A] pi.hole from 127.0.0.1
Nov 14 19:28:48 dnsmasq[974]: 460 127.0.0.1/56158 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:29:18 dnsmasq[974]: 461 127.0.0.1/34072 query[A] pi.hole from 127.0.0.1
Nov 14 19:29:18 dnsmasq[974]: 461 127.0.0.1/34072 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:29:48 dnsmasq[974]: 462 127.0.0.1/55264 query[A] pi.hole from 127.0.0.1
Nov 14 19:29:48 dnsmasq[974]: 462 127.0.0.1/55264 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:30:18 dnsmasq[974]: 463 127.0.0.1/43652 query[A] pi.hole from 127.0.0.1
Nov 14 19:30:18 dnsmasq[974]: 463 127.0.0.1/43652 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:30:48 dnsmasq[974]: 464 127.0.0.1/40608 query[A] pi.hole from 127.0.0.1
Nov 14 19:30:48 dnsmasq[974]: 464 127.0.0.1/40608 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:31:18 dnsmasq[974]: 465 127.0.0.1/34183 query[A] pi.hole from 127.0.0.1
Nov 14 19:31:18 dnsmasq[974]: 465 127.0.0.1/34183 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:31:48 dnsmasq[974]: 466 127.0.0.1/46713 query[A] pi.hole from 127.0.0.1
Nov 14 19:31:48 dnsmasq[974]: 466 127.0.0.1/46713 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:32:18 dnsmasq[974]: 467 127.0.0.1/55154 query[A] pi.hole from 127.0.0.1
Nov 14 19:32:18 dnsmasq[974]: 467 127.0.0.1/55154 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:32:48 dnsmasq[974]: 468 127.0.0.1/33070 query[A] pi.hole from 127.0.0.1
Nov 14 19:32:48 dnsmasq[974]: 468 127.0.0.1/33070 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:33:18 dnsmasq[974]: 469 127.0.0.1/44149 query[A] pi.hole from 127.0.0.1
Nov 14 19:33:18 dnsmasq[974]: 469 127.0.0.1/44149 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:33:48 dnsmasq[974]: 470 127.0.0.1/57954 query[A] pi.hole from 127.0.0.1
Nov 14 19:33:48 dnsmasq[974]: 470 127.0.0.1/57954 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:34:19 dnsmasq[974]: 471 127.0.0.1/44360 query[A] pi.hole from 127.0.0.1
Nov 14 19:34:19 dnsmasq[974]: 471 127.0.0.1/44360 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:34:49 dnsmasq[974]: 472 127.0.0.1/37819 query[A] pi.hole from 127.0.0.1
Nov 14 19:34:49 dnsmasq[974]: 472 127.0.0.1/37819 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:35:19 dnsmasq[974]: 473 127.0.0.1/33417 query[A] pi.hole from 127.0.0.1
Nov 14 19:35:19 dnsmasq[974]: 473 127.0.0.1/33417 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:35:49 dnsmasq[974]: 474 127.0.0.1/34088 query[A] pi.hole from 127.0.0.1
Nov 14 19:35:49 dnsmasq[974]: 474 127.0.0.1/34088 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:36:19 dnsmasq[974]: 475 127.0.0.1/38238 query[A] pi.hole from 127.0.0.1
Nov 14 19:36:19 dnsmasq[974]: 475 127.0.0.1/38238 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:36:49 dnsmasq[974]: 476 127.0.0.1/47870 query[A] pi.hole from 127.0.0.1
Nov 14 19:36:49 dnsmasq[974]: 476 127.0.0.1/47870 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:37:19 dnsmasq[974]: 477 127.0.0.1/53128 query[A] pi.hole from 127.0.0.1
Nov 14 19:37:19 dnsmasq[974]: 477 127.0.0.1/53128 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:37:49 dnsmasq[974]: 478 127.0.0.1/55643 query[A] pi.hole from 127.0.0.1
Nov 14 19:37:49 dnsmasq[974]: 478 127.0.0.1/55643 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:38:19 dnsmasq[974]: 479 127.0.0.1/40290 query[A] pi.hole from 127.0.0.1
Nov 14 19:38:19 dnsmasq[974]: 479 127.0.0.1/40290 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:38:49 dnsmasq[974]: 480 127.0.0.1/34196 query[A] pi.hole from 127.0.0.1
Nov 14 19:38:49 dnsmasq[974]: 480 127.0.0.1/34196 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:39:19 dnsmasq[974]: 481 127.0.0.1/56809 query[A] pi.hole from 127.0.0.1
Nov 14 19:39:19 dnsmasq[974]: 481 127.0.0.1/56809 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:39:49 dnsmasq[974]: 482 127.0.0.1/45112 query[A] pi.hole from 127.0.0.1
Nov 14 19:39:49 dnsmasq[974]: 482 127.0.0.1/45112 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:40:19 dnsmasq[974]: 483 127.0.0.1/41721 query[A] pi.hole from 127.0.0.1
Nov 14 19:40:19 dnsmasq[974]: 483 127.0.0.1/41721 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:40:49 dnsmasq[974]: 484 127.0.0.1/54308 query[A] pi.hole from 127.0.0.1
Nov 14 19:40:49 dnsmasq[974]: 484 127.0.0.1/54308 /etc/pihole/local.list pi.hole is 192.168.2.212
Nov 14 19:41:19 dnsmasq[974]: 485 127.0.0.1/57692 query[A] pi.hole from 127.0.0.1
Nov 14 19:41:19 dnsmasq[974]: 485 127.0.0.1/57692 /etc/pihole/local.list pi.hole is 192.168.2.212

rleidl · November 14, 2018, 6:45pm

will try this: ut a client DNS directly (manually) on the Pi-Hole IP address (bypassing any DNS assignment by the router). If the client connects to Pi-Hole DNS, then the router is causing the problem.

jfb · November 14, 2018, 6:48pm

This log output is showing that Pi-Hole is only receiving commands from it's own host platform, and nothing from other IP's. So, nothing on your network is using Pi-Hole as DNS server.

rleidl · November 14, 2018, 6:56pm

... set pihole as DNS on y client.- resolving does not work. no pages are loading.

jfb · November 14, 2018, 7:05pm

This caught my eye as well. Something in your setup is hiding the Pi-Hole from the rest of the network, either in your container or the router.

You'll have to do some troubleshooting here.

I would start with the Pi-Hole host platform. See if it can connect to the router, internet and ping external sites (google is usually a reliable ping).

Then get a client working on Pi-Hole. Lastly, the router.

Your debug log shows that Pi-Hole can filter domains properly, just the connection error noted above.

rleidl · November 14, 2018, 7:06pm

k, will do. Thank you.

rleidl · November 14, 2018, 7:26pm

From the pi-hole docker interface I could not ping any other host on my network. I changed settings "Interface listening behaviour to " Listen on all interfaces, permit all origins" - now my client (with pi-hole as fixed DNS) is using pihole as DNS Server and is actively blocking ads. Query logs is showing the expected entries.

rleidl · November 14, 2018, 7:38pm

host pi.hole is now showing the correct answer:
pi.hole has address 192.168.2.212

System works even if client is using router IP as DNS-Server.

system · December 5, 2018, 7:38pm

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