Hello,
as the title says, Pi-hole won't cache results for unknown query types, i.e. everything that falls into the OTHER category, plus the new query types HTTPS and SVCB.
edit: Issue extends to unknown reply types instead of unknown query types. See my next comment.
When looking at the Query Log it will also always display the Reply as N/A (0.0ms). I don't know if this is specifically a bug of the beta or if this happens on stable as well, but I'm on the beta version so that's the category I chose.
Dig results for both requests. No idea why Windows spawns 3 queries for each.
$ dig TYPE65 https.dns.netmeister.org.
; <<>> DiG 9.16.1-Ubuntu <<>> TYPE65 https.dns.netmeister.org.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31647
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;https.dns.netmeister.org. IN TYPE65
;; ANSWER SECTION:
https.dns.netmeister.org. 1252 IN TYPE65 \# 123 2D6E2031202E20616C706E3D2268332C683222206970763668696E74 3D22323030313A3437303A33303A38343A653237363A363366663A66 6537323A333930302220706F72743D22383038302220656368636F6E 6669673D225A57356A636E6C776447566B49474E7361575675644342 6F5A57787362776F3D220A
https.dns.netmeister.org. 1252 IN TYPE65 \# 25 2D6E2030207777772E6E65746D6569737465722E6F72672E0A
;; Query time: 150 msec
;; SERVER: 172.18.160.1#53(172.18.160.1)
;; WHEN: Thu Aug 26 02:05:06 CEST 2021
;; MSG SIZE rcvd: 225
$ dig TYPE65 https.dns.netmeister.org.
; <<>> DiG 9.16.1-Ubuntu <<>> TYPE65 https.dns.netmeister.org.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52474
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;https.dns.netmeister.org. IN TYPE65
;; ANSWER SECTION:
https.dns.netmeister.org. 1226 IN TYPE65 \# 25 2D6E2030207777772E6E65746D6569737465722E6F72672E0A
https.dns.netmeister.org. 1226 IN TYPE65 \# 123 2D6E2031202E20616C706E3D2268332C683222206970763668696E74 3D22323030313A3437303A33303A38343A653237363A363366663A66 6537323A333930302220706F72743D22383038302220656368636F6E 6669673D225A57356A636E6C776447566B49474E7361575675644342 6F5A57787362776F3D220A
;; Query time: 40 msec
;; SERVER: 172.18.160.1#53(172.18.160.1)
;; WHEN: Thu Aug 26 02:05:32 CEST 2021
;; MSG SIZE rcvd: 225
As you can see from the dig results, each request was answered with appropriate data and there were another 20 minutes left on the time-to-live (TTL). Despite this, Pi-hole forwarded the second query instead of answering from cache. Additionally, the Reply column shows N/A (0.0ms) even though a valid answer was received and the query most certainly was not processed instantaneously.
Here is the same behavior with the GPOS query type. Despite almost 40 minutes left on the TTL the second query was not cached.
Dig results. Again, Windows being over-enthusiastic.
$ dig gpos gpos.dns.netmeister.org.
; <<>> DiG 9.16.1-Ubuntu <<>> gpos gpos.dns.netmeister.org.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15593
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;gpos.dns.netmeister.org. IN GPOS
;; ANSWER SECTION:
gpos.dns.netmeister.org. 2368 IN GPOS "40.731" "-73.9919" "10.0"
;; Query time: 190 msec
;; SERVER: 172.18.160.1#53(172.18.160.1)
;; WHEN: Thu Aug 26 02:15:59 CEST 2021
;; MSG SIZE rcvd: 85
$ dig gpos gpos.dns.netmeister.org.
; <<>> DiG 9.16.1-Ubuntu <<>> gpos gpos.dns.netmeister.org.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17752
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;gpos.dns.netmeister.org. IN GPOS
;; ANSWER SECTION:
gpos.dns.netmeister.org. 2340 IN GPOS "40.731" "-73.9919" "10.0"
;; Query time: 50 msec
;; SERVER: 172.18.160.1#53(172.18.160.1)
;; WHEN: Thu Aug 26 02:16:27 CEST 2021
;; MSG SIZE rcvd: 85
Granted, you probably won't be seeing these other query types besides HTTPS very often. I chose GPOS here arbitrarily, any query type not known to Pi-hole will show this behavior as well. This site has set up all resource records with definitions of their content for testing:
Maybe a new generic reply type like DATA could be shown for queries of which the format of the answer is not known. (unless its NODATA of course)
And obviously showing the actual response time instead of 0.0 ms would be nice.
$ pihole -v
Pi-hole version is release/v5.4 v5.3.1-96-g58a21bee (Latest: v5.3.1)
AdminLTE version is release/v5.6 v5.5.1-65-g224f906 (Latest: v5.5.1)
FTL version is release/v5.9 vDev-9a53df6 (Latest: v5.8.1)
Not sure if the debug log will be useful but here you go:
[✓] Your debug token is: https://tricorder.pi-hole.net/YisTXm06/
, but the web release/v5.6 branch is missing the 