Document encrypted DNS for clients and the HTTP/2 and HTTP/3 web server - #1416
Draft
DL6ER wants to merge 1 commit into
Draft
Document encrypted DNS for clients and the HTTP/2 and HTTP/3 web server#1416DL6ER wants to merge 1 commit into
DL6ER wants to merge 1 commit into
Conversation
✅ Deploy Preview for pihole-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
6 tasks
DL6ER
force-pushed
the
new/encrypted-dns
branch
3 times, most recently
from
August 9, 2026 04:46
a233bf5 to
2eb4368
Compare
Signed-off-by: DL6ER <dl6er@dl6er.de>
DL6ER
force-pushed
the
new/encrypted-dns
branch
from
August 9, 2026 04:59
2eb4368 to
9430777
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation for the inbound DoT/DoH/DoQ server and for the HTTP/2 and HTTP/3 support of FTL's web server.
Related FTL PRs:
dns.dot/dns.doqbecome port numbers, default853,0disables)This is a draft on purpose. It already describes the final state, i.e., the ports as numbers rather than the booleans currently in
development, but docs.pi-hole.net servesmasterdirectly, so merging is publishing: these pages must not go live before the features ship. This PR is therefore to be merged with the release of v7.0, not when pi-hole/FTL#3012 lands indevelopment.New page
docs/ftldns/encrypted-dns.md("Encrypted DNS" in the FTLDNS menu):853, DoQ (RFC 9250) on UDP853, and DoH (RFC 8484) at/dns-queryon every TLS-enabledwebserver.port. DoT and DoQ share the port number without colliding; DoH has no port of its own and follows the web server.853, as that is what clients try first.dns.listeningMode, plus a warning against exposing the resolver to the Internet.kdig +tls,kdig +quic,curl) and where to enter this on Android, Apple devices, Firefox and routers./dns-queryis refused with426 Upgrade Requiredinstead of silently resolving.Changes to existing pages:
docs/ftldns/webserver.md- a section on HTTP/2 and HTTP/3: negotiated through ALPN with nothing to configure, CivetWeb still serving HTTP/1.1 behind the TLS front end,Alt-Svcadvertisingh3, and the practical firewall consequence that HTTP/3 needs UDP on the same port number as HTTPS.docs/api/tls.md- the certificate is now also presented to DoT/DoH/DoQ clients; a section on the automatic renewal of self-generated certificates (webserver.tls.validity, renewed two days before expiry,0to leave an own certificate alone); and a note that TLS 1.2 is the lowest accepted version.docs/main/prerequisites.md- port853added to the ports table, with notes that DoH rides the HTTPS ports and that HTTP/3 uses UDP on the HTTPS port number.Still open as separate follow-ups: the docker documentation (ports and an example
compose.yaml), the plaintext-DoH-behind-a-reverse-proxy option once it exists, and the per-query transport display in the query log.