[GH-ISSUE #504] Add padding support for DNS-over-TLS (and HTTPS) via EDNS padding #509

New issue

Open

opened 2026-03-15 22:52:49 +03:00 by kerem · 0 comments

kerem commented

2026-03-15 22:52:49 +03:00

Owner

Originally created by @bluejekyll on GitHub (May 31, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/504

See: https://tools.ietf.org/html/rfc7830

The only complexity I really see here is that this is probably incompatible with SIG0, as SIG0 is always added to the end of the message. #278 is about using mTLS for dynamic updates, making SIG0 unnecessary in TLS contexts.

The current logic on how EDNS options are associated to the DNS packet will need to be revisited, as this needs to be calculated after the rest of the message is serialized.

Originally created by @bluejekyll on GitHub (May 31, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/504 See: https://tools.ietf.org/html/rfc7830 The only complexity I really see here is that this is probably incompatible with SIG0, as SIG0 is always added to the end of the message. #278 is about using mTLS for dynamic updates, making SIG0 unnecessary in TLS contexts. The current logic on how EDNS options are associated to the DNS packet will need to be revisited, as this needs to be calculated after the rest of the message is serialized.