4 ms·

Only if you are using DNS over https.

• nilsb 6y ago
  One could probably do DTLS over DNS.
• m463 6y ago
  dig hi.001.mydomain.com dig how.002.mydomain.com dig are.003.mydomain.com dig you.004.mydomain.com
  • cookiengineer 6y ago
    You don't need that. TTL zero and dns query header IDs are enough. You could even implement a threaded chat, using the id as a responded-to sorting mechanism. Also, TXT can contain binary data, and when using DNS over TCP is pretty much unlimited in frame size.
• zamadatix 6y ago
  Why not https over DNS :)
• yardstick 6y ago
  If you are using https/TLS it doesn’t really matter what inner protocol you use, because it’s encrypted so third parties can’t validate it.
  • toast0 6y ago
    If you're using DNS over TLS (or HTTPS, whatever) to the origin, sure third parties are limited. If you're doing DNS over TLS to a public resolver that then transmits to an origin, that resolver is a third party that can see requests and responses.
    • silon42 6y ago
      I guess this is reason enough to block that (DNS over TLS)