I update Pi.hole to 5.5 version
root@ZeroPi-DNS:~# nslookup pi.hole
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
*** Can't find pi.hole: No answer
root@ZeroPi-DNS:~# nslookup 192.168.255.250
Server: 127.0.0.1
Address: 127.0.0.1#53
250.255.168.192.in-addr.arpa name = pi.hole.
root@ZeroPi-DNS:~# pihole -v
Pi-hole version is v5.5 (Latest: v5.5)
AdminLTE version is v5.7 (Latest: v5.7)
FTL version is v5.10.2 (Latest: v5.10.2)
my custom settings
root@ZeroPi-DNS:/etc/dnsmasq.d# cat lan-dns
# GATEWAY
# 192.168.255.254
server=/255.168.192.in.addr.arpa/192.168.255.254
server=/lan.vitko-core.ru/192.168.255.254
# IP => Daomain
server=/255.30.172.in-addr.arpa/172.30.255.254
server=/254.30.172.in-addr.arpa/172.30.254.254
# Domain => IP
server=/172.30.255.254/172.30.255.254
server=/172.30.254.254/172.30.254.254
Why Can't find pi.hole: No answer?!
jfb
October 6, 2021, 1:06pm
2
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:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
https://tricorder.pi-hole.net/rzSjp77A/
root@ZeroPi-DNS:/etc/dnsmasq.d# cat * | grep "pi.hole"
# (c) 2017 Pi-hole, LLC (https://pi-hole.net)
# (c) 2021 Pi-hole, LLC (https://pi-hole.net)
# We do not include the ".local" rule ourselves, see https://github.com/pi-hole/pi-hole/pull/4282#discussion_r689112972
root@ZeroPi-DNS:/etc/dnsmasq.d# cat /etc/hosts
127.0.0.1 ZeroPi-DNS ZeroPi-DNS.lan.vitko-c.ru localhost
127.0.1.1 ZeroPi-DNS
root@ZeroPi-DNS:/etc/dnsmasq.d#
and i used pihole -r
The problem has not gone away
jfb
October 6, 2021, 5:52pm
5
Run this command and post the output.
nslookup pi.hole 192.168.255.250
Then look in the dnsmasq log at /var/log/pihole.log and find the query, forward (if any) and reply for this request and post them as well.
root@ZeroPi-DNS:~# nslookup pi.hole
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: pi.hole
Address: 192.168.255.250
I can't understand, at the moment everything works. I can say that on the screenshot 2 items ignored the save button and were always turned on. I reinstalled pihole and restarted the system, the problem remained, but now it is gone. IT IS MAGIC
or I'm guessing that there is a problem with the transition of DNS Forwarder to DNS Resolver.
i'm not sure about that, but:
before
after
or the system did not cope with the requests and received a bug?
GATEWAY = pfSense as DHCP server (DNS: 192.168.255.250 - pi.hole), there were 245514 requests, afte 4002 requests
system
Closed
October 27, 2021, 7:15pm
9
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.