We did the same thing w/ JSON responses: https://www.openresolve.com/
This is a bad idea outside of experimentation. Not to be used for production.
If you want to secure DNS look at QUIC, TLS, or my favorite, DNSCrypt (which I funded).
This is a bad idea outside of experimentation. Not to be used for production.
If you want to secure DNS look at QUIC, TLS, or my favorite, DNSCrypt (which I funded).
As a user, I can sure think of some countries with broken Internet access where this would come in handy.
Running DNS over HTTPS over TCP isn't needed. It doesn't solve a problem.
Doing JSON DNS for OOB DNS checks is useful since most applications speak HTTP. :-)
dns.google.com:443 true QUIC_VERSION_34 [2607:f8b0:400d:c03::8a]:443 10544469510527000173 0 None 2 9 0 9 true
An independent implementation of QUIC (are there any outside of browsers?) would probably work much the same, modulo any changes during the ongoing standardization of QUIC.
For debugging and diagnostics it is useful, for querying via a local resolver not so good.