/etc/unbound/unbound.conf.d $ ls
pi-hole.conf qname-minimisation.conf root-auto-trust-anchor-file.conf
whereas
cat qname-minimisation.conf
server:
# Send minimum amount of information to upstream servers to enhance
# privacy. Only sends minimum required labels of the QNAME and sets
# QTYPE to NS when possible.
# See RFC 7816 "DNS Query Name Minimisation to Improve Privacy" for
# details.
qname-minimisation: yes
and
dig txt qnamemintest.internet.nl +short
a.b.qnamemin-test.internet.nl.
"NO - QNAME minimisation is NOT enabled on your resolver :("
I ran a test on the web addresses listed in the referenced document (page 34 of 42 in the document) with QNAME minimisation enabled - I was able to resolve them all with dig.
I suspect that since the date of that paper (May 2015) the noted problems at the authoritative name servers have been corrected.
I am running two setups of unbound and Pi-Hole; identical but on different Pi's. One has QNAME off, the other has QNAME on. I cannot see any different in DNS resolution between the two.
Thanks for testing it so throughly. It's good to know that we don't have to expect issues from possible system provided config files that enable qname minimization without the (explicit) knowledge of the user.
I support the approach the PiHole developers take for installing add-ons (unbound, DNS over HTTPS, etc) - give detailed guides, explain the ramifications of various settings, let the user install as he/she desires. I prefer that to a "click here and it's installed" approach. I'm not that handy around Unix and I've been able to follow your guides nicely.
I've read in the feature requests for DNS over TLS the discussion on that topic. I'm in your camp on this one.
I have simply modified the qname-minimisation.conf to be set to "no". Reading jfb's information that so far he has no difference between his two configurations (one qname-minimisation on and one off) is the recommendation still to disable this?
I did this based on approx 12% of queries failing on a few of the large CDN hosts. If it is now reliable I would change it to "yes" again to benefit from better privacy.
I'd be interested in others opinions on this, thanks.