Hi there. I have update my PiHole using pihole -up and since that, it does not answer queries on 192.168.1.1 (pihole network ip). It does answer if queried 127.0.0.1.
From the machine (rasppi):
dig test.de@127.0.0.1 -> correct answer
dig test.de@192.168.1.1 -> timeout
It does listen on 192.168.1.1 (verified via netstat):
udp 0 0 0.0.0.0:53 0.0.0.0:* 1942/pihole-FTL
I had this problem a while ago, forgot what the solution was
Still i have the "feeling" that pihole is very unstable so far...
Anyone can help me what can cause this? the web-interface as well as log dont give any clue...
Thanks for your help and time. I think i found the problem myself, and again, sorry for opening the topic. I have a bridge device(br0) actually holding the ip 192.168.1.1 instead of eth0.
I have done the following:
Created the file /etc/dnsmasq.d/99-mypi.conf
Inserted "interface=br0"
Since that network resolves on 192.168.1.1 work again Is that a way to keep that permanent and "survive" a next "pihole -up" ?
I think in my last config i commented out "interface=eth0" and replaced it with "interface=127.0.0.1,192.168.1.1" - thats why it was working, but i did not use an extra config so that one was overwritten by the update (as clearly stated in the file)
Sorry, thats not PiHole's fault. I use the br0 as wifi access point.
so that one was overwritten by the update (as clearly stated in the file)