mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 19:25:56 +03:00
[GH-ISSUE #1870] Configuration of bind interface for resolver #800
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#800
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hottea773 on GitHub (Jan 5, 2023).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1870
I'd like to be able to set the interface used by the resolver. This is a similar concept to https://github.com/bluejekyll/trust-dns/pull/1586, but I want to be able to set the interface. This is desired because when working with VRFs, one cannot bind to an address without first being on the correct interface.
Ideally this would be resolved by https://github.com/bluejekyll/trust-dns/issues/1863 (so that I could use https://docs.rs/socket2/latest/socket2/struct.Socket.html#method.bind_device and create a socket from there), but could also be resolved by a similar approach to https://github.com/bluejekyll/trust-dns/pull/1586.
Feel free to delete this Issue if you think that the lesser approach is not something you'd like to consider and it can just be rolled into the pass in a socket issue.
@hottea773 commented on GitHub (Apr 26, 2023):
Closing as https://github.com/bluejekyll/trust-dns/pull/1876 resolves this