I updated my pihole software on my RaspberryPi 4 to:
- Pi-hole [v5.11.4]
- FTL [v5.16.1]
- Web Interface [v5.13]
and noticed that when I tried to enable a whitelist item in order to report a spammed web site that it didn't work. I had to re-add the item in order to have it be enabled. I then updated the Pi fully and rebooted to see if there was something cached or otherwise hanging on. There was no change. Prior to this update, I could update a whitelist item via the web interface (enable/disable, add a comment, etc.), the effect was immediately visible to a ping or nslookup.
This is the output from the pihole's console demonstrating this current bad behavior:
pi@ThePiHole:~ $ pihole -w --list | grep ojrq 40: www.ojrq.net (enabled, last modified Wed, 20 Jul 2022 11:17:56 -0700) pi@ThePiHole:~ $ ping www.ojrq.net PING www.ojrq.net (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.091 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.048 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.092 ms ^C --- www.ojrq.net ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 78ms rtt min/avg/max/mdev = 0.048/0.077/0.092/0.020 ms pi@ThePiHole:~ $ nslookup > server Default server: 127.0.0.1 Address: 127.0.0.1#53 > www.ojrq.net Server: 127.0.0.1 Address: 127.0.0.1#53 Name: www.ojrq.net Address: 0.0.0.0 Name: www.ojrq.net Address: :: > exit
I'm surprised that it hasn't been noted if it is widespread, but maybe it's just my installation? I am also running unbound to act as my own local DNS so pihole is going against 127.0.0.1#5353 for lookups.