QUOTE(Moogle Stiltzkin @ Sep 11 2024, 05:19 AM)
is dot or doh better?
i did dot at router, cauz my users r not savvy enough to go browser enable doh (go figure).
You can test here if it's working or not
https://one.one.one.one/help/got too involved as i am working/worked on DNS proxying the past few nights.
an endeavour which itself involved research purposes, with the achieved outcome is obviously meant to facilitate future research purposes.
so far i have DoH working in iphone, ipad, windows, and linux.
android unfortunately requires DoT, which i am avoiding because its default port tcp/853 can be detected and thus subject to blocking - and worst, hijacking.
--
i'm ignoring cost of creating and cost of deciphering DNS wire payload, which is applicable to each below.
DNS
no udp/53 protocol penalty
DNS-over-TLS
tcp/853; cost of establishing TCP session, cost of negotiating secure TLS session, cost of tearing TCP session
DNS-over-HTTP/1, DNS-over-HTTP/1.1, DNS-over-HTTP/2
tcp/443; cost of establishing TCP session, cost of negotiating secure TLS session, cost of parsing HTTP request and response, cost of tearing down TCP session
DNS-over-HTTP/3, which runs over QUIC
udp/443; cost of negotiating QUIC session, cost of parsing HTTP request and response
https://www.f5.com/glossary/quic-http3
--
instead of using DoH-proxy reinvented by people out there, i decided to use nginx as my DNS-over-HTTPS forwarder. no need to reinvent the wheel.
immediately can support all HTTP/1 to HTTP/3, tcp and quic protocols.
and specifically choosing nginx; because i can hide my DNS-over-HTTPS entry point behind normal web hosting.
Unless one knows the exact
https://what-is-my-exact-name/, you shouldn't be able to identify it nor use it. Hiding in plain sight.
--
(oh, yes. i'm bragging.)
This post has been edited by Oltromen Ripot: Sep 11 2024, 12:48 PM