[GH-ISSUE #2085] DoH3 grease setting #879

Open
opened 2026-03-16 00:44:19 +03:00 by kerem · 0 comments
Owner

Originally created by @daxpedda on GitHub (Oct 31, 2023).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2085

Is your feature request related to a problem? Please describe.
As a follow-up in https://github.com/hickory-dns/hickory-dns/pull/2077 I was looking into how to integrate a configuration that can disable HTTP/3 grease.

Describe the solution you'd like
A setting, preferably in NameServerConfig, that allows HTTP/3 grease to be disabled for specific DNS resolvers.

Describe alternatives you've considered
Alternatively it could be put in ResolverOpts or maybe even in TlsClientConfig, but this setting is actually unrelated to TLS.

Additional context
The reason why I thought this might require some discussion is that this is just a workaround for a bug, see https://github.com/hyperium/h3/issues/206. So it might not be desirable to add this setting at all.

There might be better case for putting it into ResolverOpts, because AFAIK the only reason why anybody would like to disable grease, apart from circumventing bugs, is to save on a couple of bytes. So it might make more sense to make it a less specific (compared to NameServerConfig) setting.

Originally created by @daxpedda on GitHub (Oct 31, 2023). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2085 **Is your feature request related to a problem? Please describe.** As a follow-up in https://github.com/hickory-dns/hickory-dns/pull/2077 I was looking into how to integrate a configuration that can disable HTTP/3 grease. **Describe the solution you'd like** A setting, preferably in `NameServerConfig`, that allows HTTP/3 grease to be disabled for specific DNS resolvers. **Describe alternatives you've considered** Alternatively it could be put in `ResolverOpts` or maybe even in `TlsClientConfig`, but this setting is actually unrelated to TLS. **Additional context** The reason why I thought this might require some discussion is that this is just a workaround for a bug, see https://github.com/hyperium/h3/issues/206. So it might not be desirable to add this setting at all. There might be better case for putting it into `ResolverOpts`, because AFAIK the only reason why anybody would like to disable grease, apart from circumventing bugs, is to save on a couple of bytes. So it might make more sense to make it a less specific (compared to `NameServerConfig`) setting.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#879
No description provided.