All the queries for this domain have been forwarded to the same unbound resolver (fdaa:bbcc:ddee:2::5552#5552 - see screenshot below), in fact, of all the queries performed since the restart this morning, 56.2% have been answered by the IPv6 resolver, 6.6%cached and 36.9%blocklist. Currently, pihole doesn't like the IPv4 (127.10.10.2#5552) resolver very much (slower).
Not related to this issue but you don't need to use IPv6 over a local connection to the same host. Just use the 127 address. You're over complicating a lot of things.
DL6ER did release an update for the branch new/CNAME_inspection_detailsthis morning, run pihole -up and don't forget to clear the browser cache. Since the update, clicking on the domain in the query log shows the relevant queries.
I would really appreciate if you also list your configuration, and use my method to identify a recent occurrence of the problem we have been seeing. If NOT, I'm afraid the bug report will be closed without further investigation (independent source).
pihole checkout ftl new/CNAME_inspection_details
pihole checkout web new/CNAME_inspection_details
Pi-hole version is v4.3.2-391-ge0b3405 (Latest: v4.3.2)
AdminLTE version is v4.3.2-363-g90a09d1c (Latest: v4.3.2)
FTL version is vDev-122a701 (Latest: v4.3.1)
Can't use LTD (lighttpd issue). Can use Query Log - Show all
apt-get update on the client gives expected results.
msn.com in browser gives one query (A) OK. I whitelisted msn.com. Next domain in chain is blocked.
When I remove msn.com from the whitelist it is Blocked (gravity, CNAME)
Mine are. Don't know about @jpgpi250.
Can I go back to release/v5.0?
Will the patch be merged before release? I know I will loose the patch in the meantime.
The web interface did its work anyway. I added the missing linefeed, stopped lighttpd, deleted its large error log, restartet it and no error occured so far.