mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #251] Support user-specified location for /etc/hosts file #417
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#417
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 @briansmith on GitHub (Oct 24, 2017).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/251
Some uses of Trust-DNS, in particular some kinds of tests for applications that use Trust-DNS, would benefit from being able to specify the path of the /etc/hosts file. Perhaps instead of having a boolean flag indicating whether to use /etc/hosts, the setting could instead become a
PathBufthat contains the path to the file?@briansmith commented on GitHub (Oct 24, 2017):
In particular, it seems like it would be useful to have this functionality for the purposes of testing the implementation of
Hosts, especially on platforms that don't have/etc/hostsand/or where/etc/hostsis in a different place. For example, it would be great to be able to run all the tests forHostson Windows so that WIndows-based contributors can be more sure that they didn't break anything related to it before submitting a PR.(As it is now, rustc emits a bunch of warnings when building this code for Windows because it is dead on Windows.)