Unknown status in query log after Update to v3.2

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

I have fhem and pi-hole installed on a Raspberry Pi 3.
After update pi-hole to v3.2, I expected that the querys which made by fhem's lan-ping-module are shown as OK in the query log (like it was before the update).

Actual Behaviour:

Queries which made by the lan-ping-module in fhem are shown with status unknown in query log.

Debug Token:

z90usnziq7

I searched here and found this thread with exact the same behavior.
I also use the /etc/pihole/lan.list file.
So I had temporarily removed this file (and restarted dnsmasq and run pihole -g), but the issue was still the same.

What is going wrong?
If I run nslookup galaxy-s7-andi.▓▓▓▓▓.box, I get the right response and the query has status OK in the log.

While the Query Log shows unknown status, I see while tailing pihole.log that the query has been forwarded to the router (192.168.0.1):

query_1
query_11492×243 43.4 KB

query_2
query_2965×248 85.4 KB

2

Does the Unknown status "survive" a restart of FTL ?

Try

sudo service pihole-FTL restart
3

Even after restart of FTL nothing changed on behavoir.
(I had also restarted the raspberry yesterday) :confused:

4

Same problem after update to V 3.2. (192.168.1.1 is router)
Restarting FTL didn't change anything. No /etc/pihole/lan.list file.

Debug Token:
4y7glu53ci

query
query1273×1198 135 KB
Terminal
Terminal1164×1185 364 KB

5

I'm unable to reproduce ... please run

tail -n 20 /var/log/pihole-FTL.log | pihole tricorder

to securely upload the last 20 lines of FTL's log file to our server. Please provide the token afterwards.

6

Ok.
Response was token q6yv59zek9

7

Okay, it seems to be a problem with mixed cases domains (like GooGle.coM), I'm working on this right now.

8

I opened an issue report to be able to keep track on GitHub

9

Bug fix incoming

10

Thank you very much for the fast responses and the bugfix :blush: