I upgraded to v6 recently and after fixing the problems I am left with 1 annoyance which I cannot solve. I use pihole local DNS to access my few servers. They are added via web Local DNS records: server1.lan 192.168.1.2 server2.lan 192.168.1.3 The problem is, the pihole is running on server2 and …

I did full clean start and it works there. I have no idea why. I added my 5 custom list and 6 local hostnames and replaced with old docker. So it works now. If someone wants to investigate I can zip old and new etc-pihole folder for investigation.

How did that nslookup register in Pi-hole's Query Log? sudo grep server2.lan /var/log/pihole/pihole.log

Feb 26 10:35:43 dnsmasq[58]: query[A] server2.lan from 192.168.1.8 Feb 26 10:35:43 dnsmasq[58]: Pi-hole hostname server2.lan is 0.0.0.0

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 if you run your Pi-hole as a Docker container: docker exec -it <pihole-container-name-or-id> pihole -d where you substi…

debug log - https://tricorder.pi-hole.net/b2UfrjzO/ notes about real dns names. pihole runs on hostname "rp3" with IP 192.168.1.3 the 0.0.0.0 is returned for rp3.lan

Your debug log shows that you run your Pi-hole as a Docker container. Your local DNS record definitions look ok: hosts = [ (…+6 names…) "192.168.1.3 rp3", "192.168.1.3 rp3.lan" ] ### CHANGED, default = [] But even though pihole-FTL/dnsmasq reads the resulting defini…

Yes, its docker. rp3:~$ docker exec -it pihole cat /etc/hosts # Your system has configured 'manage_etc_hosts' as True. # As a result, if you wish for changes to this file to persist # then you will need to either # a.) make changes to the master file in /etc/cloud/templates/hosts.debian.tmpl # b.)…

Watching this closely as I experience the same issue. I think I'd help if nsswitch were preferring dns over files, as my Pihole is using DHCP and I configured it to forward requests to my router. So the own hostname in /etc/hosts is 127.0.1.1 (which is very common) and Pihole prefers (nsswitch) fil…

For me even pi.hole lookup returns zeroes. $ nslookup pi.hole Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: pi.hole Address: 0.0.0.0 interestingly, if I choose different name as hostname and add that one for 192.168.1.3, it returns correctly: $ nslook…

[image] MostFrabjous: Pihole prefers (nsswitch) files over dns Pi-hole is DNS exclusively, it does not concern itself with nsswitch at all, but it reads /etc/hosts. Are you running your Pi-hole as a container, MostFrabjous? Juraj_jiv, I tried to recreate your issue by editing /etc/hosts in…

So nss is out of the picture. Good to know. I'm running pihole in a container too. I'm forwarding requests from my local LAN to my router whichs also serving DHCP and DNS. The queries for all the hosts on my network get forwarded to my router and work well, but pihole's FQDN (pi.beeb.at) gets resol…

Local DNS resolves as 0.0.0.0 for itself

Help Community Help

MostFrabjous March 2, 2025, 9:37am 21

I'd like to diff them!