[GH-ISSUE #2510] Allow adding dns options in hickory_client::client::Client #1007

Closed
opened 2026-03-16 01:15:21 +03:00 by kerem · 3 comments
Owner

Originally created by @mat813 on GitHub (Oct 16, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2510

Is your feature request related to a problem? Please describe.

I rewrote a small utility called dnstracer into rust https://crates.io/crates/dnstracer and there are a couple of flags I was not able to really implement, those are setting the EDNS0 bit when making a query, and setting the EDNS0 buffer.

The code I use to make each dns query is here https://gitlab.com/mat813/dnstracer-rs/-/blob/v0.9.1/src/resolver.rs?ref_type=tags#L227-241

Describe the solution you'd like

Would like to be able to set more options DNS options in hickory_client::client::Client.

Describe alternatives you've considered

I looked into the code and there is a use_edns field in AsyncClient, but I could not figure out how to set it when using the SyncClient.

Originally created by @mat813 on GitHub (Oct 16, 2024). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2510 **Is your feature request related to a problem? Please describe.** I rewrote a small utility called dnstracer into rust <https://crates.io/crates/dnstracer> and there are a couple of flags I was not able to really implement, those are setting the EDNS0 bit when making a query, and setting the EDNS0 buffer. The code I use to make each dns query is here <https://gitlab.com/mat813/dnstracer-rs/-/blob/v0.9.1/src/resolver.rs?ref_type=tags#L227-241> **Describe the solution you'd like** Would like to be able to set more options DNS options in hickory_client::client::Client. **Describe alternatives you've considered** I looked into the code and there is a use_edns field in AsyncClient, but I could not figure out how to set it when using the SyncClient.
kerem closed this issue 2026-03-16 01:15:26 +03:00
Author
Owner

@djc commented on GitHub (Oct 16, 2024):

I'd suggest just using AsyncClient and wrapping it in a block_on() call or similar. Any reason you're avoid the async API?

<!-- gh-comment-id:2416881216 --> @djc commented on GitHub (Oct 16, 2024): I'd suggest just using `AsyncClient` and wrapping it in a `block_on()` call or similar. Any reason you're avoid the async API?
Author
Owner

@mat813 commented on GitHub (Oct 16, 2024):

I am not trying to avoid the async API, I found examples of how to work with the Sync API, and as the utility I am writing is simple, I don't need any async features.

<!-- gh-comment-id:2417291640 --> @mat813 commented on GitHub (Oct 16, 2024): I am not trying to avoid the async API, I found examples of how to work with the Sync API, and as the utility I am writing is simple, I don't need any async features.
Author
Owner

@djc commented on GitHub (Jan 20, 2025):

The synchronous Client API was removed in #2521.

<!-- gh-comment-id:2602484116 --> @djc commented on GitHub (Jan 20, 2025): The synchronous `Client` API was removed in #2521.
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#1007
No description provided.