Actual Behaviour:
Pihole is not responding to DNS requests.
I am unable to find a debug log with that token. Please generate and upload a second log.
https://tricorder.pi-hole.net/wzatsi759c
Is this one working ?
Yes. Thanks.
No obvious problems shown in the debug log. Let's take a look at the traffic the Pi-hole has processed in the past 24 hours and do a few tests from a client.
From the Pi terminal, please run the following command and post the output:
echo ">overTime >quit" | nc localhost 4711
From a connected client PC/laptop, etc, please run the following commands on the terminal or command prompt of that client and post the output:
nslookup pi.hole
nslookup pi.hole 192.168.100.10
Do I have to paste the output of
echo ">overTime >quit" | nc localhost 4711
nslookup pi.hole
;; connection timed out; no servers could be reached
nslookup pi.hole 192.168.100.10
Server: 192.168.100.10
Address: 192.168.100.10#53
Name: pi.hole
Address: 192.168.100.10
Apologies - I copied/pasted the wrong command. That's not what we need (yet). This is what we need now:
echo ">stats >quit" | nc localhost 4711
If this is a Windows client, please post the output of ipconfig /all
If a Mac, please post output of scutil --dns
No problem,
`echo ">stats >quit" | nc localhost 4711`
domains_being_blocked 91674
dns_queries_today 260519
ads_blocked_today 227
ads_percentage_today 0.087134
unique_domains 2053
queries_forwarded 15858
queries_cached 62773
clients_ever_seen 8
unique_clients 8
dns_queries_all_types 260519
reply_NODATA 5845
reply_NXDOMAIN 297
reply_CNAME 4277
reply_IP 7126
privacy_level 0
status enabled
I'm using linux hosts.
ifconfig -a and /etc/resolv.conf
> $ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.20 netmask 255.255.255.0 broadcast 192.168.100.255
inet6 fe80::d6c9:efff:fe53:1e11 prefixlen 64 scopeid 0x20<link>
ether d4:c9:ef:53:1e:11 txqueuelen 1000 (Ethernet)
RX packets 104030719 bytes 100535815247 (93.6 GiB)
RX errors 0 dropped 2371 overruns 0 frame 0
TX packets 97905560 bytes 110039345289 (102.4 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17 memory 0xd4700000-d4720000
>
>lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 48662018 bytes 62972810826 (58.6 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 48662018 bytes 62972810826 (58.6 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
>wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 96:4c:2c:e7:61:1d txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
$cat /etc/resolv.conf
>nameserver 127.0.0.1
>search lan
Since the Linux device is using itself as nameserver, it appears none of the DNS queries are making it to Pi-hole. So, that device does not use Pi-hole for DNS.
This explains the two nlsookup outputs.
Okay so I have to set it to get the dns server address from the pi dhcp server ?
Either that, or manually map it to the Pi-hole DNS IP.
Am already using pihole dhcp and my Windows clients and the fire stick can resolv domains. So I’m wondering why should I manually insert the dns on every single Linux server and why isn’t it getting the dns server from dhcp as other systems.
Look in /var/log/pihole.log and /var/log/pihole.log.1 for DHCP transactions from this device. See if any exist and if so, the result of the transaction.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.